GitLab

schema_change: removed analysis_stats[_monitor].num_required_workers, substituted with AS::estimate_num_required_workers()

Added 'meadow_user' to Worker object+schema which is now routinely recorded. Also renamed 'host' to 'meadow_host' for consistency

schema_patch_of_a_patch: no need to enforce certain seconds to be INT (a particular limitation of LSF)

schema_change: detect and register RELOCATED events that used to mess up things on LSF 9.0 ("job rescheduled" in LSF parlance)

ResourceDescription expanded to include both submission_cmd_args and worker_cmd_args. Both args can be specified in a PipeConfig file.

schema change: turned all VARCHAR(<255) into VARCHAR(255) -- should improve experience with long host namest (thanks, MichaelP!)

Updated schema diagram and description file that include param_id_stack and accu_id_stack in job table.

"parameter stack" implementation using two extra fields in job table. Accu content intended for any job_id has preference over Input_id content for the same job.

Schema change: changed the data type of monitor.analysis to TEXT as per Michael Paulini's suggestion, to fit more and longer analysis names.

use SqlSchemaAdaptor to detect the current code's sql version and record it in 'hive_meta' (leave it out of tables.*sql* files)

move Core 'schema_version' out of tables.* files into HiveGeneric_conf (via ApiVersion), expose it for manipulation and make it available to PipeConfigs

new 'hive_meta' table to keep hive_sql_schema_version (=number of patches), hive_pipeline_name and hive_use_triggers

Copied the @-tag annotation from tables.sql to tables.sqlite. Unlike the original mysql version, the SQLite version gives no warnings when processed by sql2html.pl

change of default behaviour: hive_capacity is now off by default (=NULL); setting hive_capacity=0 or analysis_capacity=0 stops scheduling AND specialization to a particular analysis

added a new per-analysis "analysis_capacity" limiter for cases where users want to limit analyses independently

Introduced a new 'NO_ROLE' cause_of_death for failures during specialization (not so much of an error, really!)

capture Worker's death message during the new 'SPECIALIZATION' status in job_message/msg (thanks, Thomas!)

feature: jobless workers will now leave module compilation errors in the job_message table (thanks, Kathryn!)