GitLab

changed the meaning of 'num_required_workers' to "total estimated number of workers needed for this analysis" ( 'num_running_workers' is now included in it )

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

(multi-meadow scheduler) restrict the set of analyses that a worker with a given meadow_type can specialize into

introduced semaphored_job_count, renamed unclaimed_job_count-->ready_job_count, changed reporting, fixed hive_capacity=0

moved failed_job_tolerance, max_retry_count, can_be_empty and priority columns from analysis_stats to analysis_base

added specific defaults into analysis_stats and analysis_stats_monitor; re-ordered the fields for easier navigation

make AnalysisStats a rearrangeable EnsEMBL-style constructor, a proper store method and other preparations

replaced rc_id by resource_class_id throughout the schema and added the foreign keys on resource_class_id

Removed maximise_concurrency and added analysis_stats.priority to guide the scheduler; improved scheduler and LSF meadow

big renaming of hive->worker, analysis_job->job, analysis_job_file->job_file, analysis_job_id->job_id, worker.beekeeper->worker.meadow_type, etc

testing the idea of analyses that can be empty for blocking purposes (it does not block while it is empty)