locked jobs prevent other jobs from running
Categories
(Socorro :: General, defect, P2)
Tracking
(Not tracked)
People
(Reporter: willkg, Assigned: willkg)
Details
Attachments
(1 file)
cronrun shouldn't block on locked jobs. If it encounters a locked job, it should skip over it and try to run other things.
Right now, it looks like locked jobs are preventing anything else from running.
This bug covers fixing that.
|
Assignee | |
Comment 1•5 years ago
|
||
Let me clarify so that future me isn't annoyed at present me because I didn't include all the relevant details.
Today I did a push to production. Seems like the crontabber node was running the bugassociations job when it was killed, so it was marked as ongoing in the db. When the new crontabber node came online, it went through the available jobs to run the ones that needed running, but when it hit bugassociations, it kicked up an OngoingJobError and then halted--it should have continued through the list of jobs to try to run the other ones. Because it wasn't running any of the jobs, that kicked up an alert since there hadn't been any crontabber jobs in 2 hours.
That's the whole story.
|
|
Assignee | |
Comment 2•5 years ago
|
||
Grabbing this to do now.
|
|
Assignee | |
Comment 3•5 years ago
|
||
|
|
Assignee | |
Comment 4•5 years ago
|
||
|
|
Assignee | |
Comment 5•5 years ago
|
||
This was deployed just now in bug #1608229.
Description
•