Closed
Bug 1407671
Opened 7 years ago
Closed 7 years ago
figure out crontabber in new infrastructure
Categories
(Socorro :: General, task)
Socorro
General
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1406019
People
(Reporter: willkg, Unassigned)
References
Details
Crontabber runs in a docker container in a script that's an infinite loop with 5 minute waits. When we do a deploy, we want old-crontabber to finish up what it's doing (which could take minutes) and then stop doing things. However, during a deploy, we might have run a migration that affected the database that's being used by the job the old-crontabber is using. In that case, old-crontabber is hosed, things happen that are probably fine, but old-crontabber doesn't update the bookkeeping table regarding running the job. Do we change crontabber bookkeeping? Do we change the timeout values for "stale jobs"? Do we add poisoning to old-crontabber so that it stops? This bug covers figuring out all that stuff and making it work.
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•