Skip to content
Snippets Groups Projects
Commit ff6ee7cb authored by Jessica Severin's avatar Jessica Severin
Browse files

on job reset don't reset the hive_id so when debugging one can track the

failed job to the failed worker.
parent 8c9c1484
No related branches found
No related tags found
No related merge requests found
......@@ -383,7 +383,7 @@ sub reset_dead_jobs_for_worker {
my ($sql, $sth);
#first just reset the claimed jobs, these don't need a retry_count index increment
$sql = "UPDATE analysis_job SET job_claim='', hive_id=0, status='READY'".
$sql = "UPDATE analysis_job SET job_claim='', status='READY'".
" WHERE status='CLAIMED'".
" AND hive_id='" . $worker->hive_id ."'";
$sth = $self->prepare($sql);
......@@ -394,7 +394,7 @@ sub reset_dead_jobs_for_worker {
# an update with select on status and hive_id took 4seconds per worker to complete,
# while doing a select followed by update on analysis_job_id returned almost instantly
$sql = "UPDATE analysis_job SET job_claim='', hive_id=0, status='READY'".
$sql = "UPDATE analysis_job SET job_claim='', status='READY'".
" ,retry_count=retry_count+1".
" WHERE status in ('GET_INPUT','RUN','WRITE_OUTPUT')".
" AND retry_count<5".
......
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment