GitLab

use when one knows all the workers are done running, so that any worker
not registered properly is assumed to be a fatality.

job reseting.  This allowed direct UPDATE..WHERE.. sql to be used.
Also changed the retry_count system: retry_count is only incremented
for jobs that failed (status in ('GET_INPUT','RUN','WRITE_OUTPUT')).
Job that were CLAIMED by the dead worker are just reset without
incrementing the retry_count since they were never attempted to run.
Also the fetching of claimed jobs now has an 'ORDER BY retry_count'
so that jobs that have failed are at the bottom of the list of jobs
to process.  This allows the 'bad' jobs to filter themselves out.

created registered to the LSF beekeeper, and the 'dead' check is done only
where the beekeeper is LSF and it's 15minutes overdue for it's checkin.
The check is done with an ssh to the workers registered host machine and
a 'ps' command to see if the registered process_id of the worker is still
running.  This allows jobs to be submitted via lsf arrays (which only give
a single LSF job id for the entire array), but still allows each worker
to be checked separately.

compute resource

Modified the way to build the worker_cmd, so that it allows now to add -limit $batch_size when the hive_capacity is < 0.

analysis_id to identify which analysis this worker is to use

need that vacation ;-)

Removed single quote around a question mark in the prepare statement. Otherwise it is not considered as an argument to be passed in the execute statement later on

defined in the analysis_stats table

(was still using the original idea of setting batch_size as
constant in the RunnableDB class).  Need to deprecate that idea.

state of all jobs on the hive.  added get_analysis method to
AnalysisStates which loads the analysis for the analysis_id.  Modified
print_stats to produce a more descriptive table of stats.

needed clutches and prints them for the user with 'bsub' commands which
then the user can choose to run or modify

analyses by fetching all the control rules and checking the distributed
conditions that they are all 'DONE'

analysis objects adaptor to fetch the corresponding stats object.
Important to use correct db connection since the analysis objects may be
network distributed across multiple databases

Bio::EnsEMBL::DBSQL::DBAdaptor to match symetry with core,pipeline,compara
This means I can remove all 'hive' adaptors from compara now and the
URLFactory now returns by default a Hive::DBSQL::DBAdaptor.
This also means I can make my graph configuring runnableDBs really
adaptible to run on both Pipeline and Hive systems by doing
if($self->db->isa('Bio::EnsEMBL::Pipeline::DBAdaptor')) {...}
if($self->db->isa('Bio::EnsEMBL::Hive::DBAdaptor')) {...}

when ALL of their conditions are 'DONE')