Closed
Bug 1518780
Opened 6 years ago
Closed 5 years ago
Move the seta-analyze-failures celery beat task to Heroku scheduler
Categories
(Tree Management Graveyard :: Treeherder: SETA, enhancement, P3)
Tree Management Graveyard
Treeherder: SETA
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: emorley, Unassigned)
References
Details
(Split out of bug 1176492)
Currently the seta-analyze-failures task is run every 1 day using a celery beat task. However for the reasons in bug 1176492 comment 0 we're trying to move away from these.
To achieve this we'll have to:
- add a Django management command for running the task (if it doesn't already exist), making sure to add it to the annotation list in newrelic.ini too
- remove the task from
CELERYBEAT_SCHEDULE
intreeherder/config/settings.py
(along with its queues underCELERY_QUEUES
), and fromProcfile
+ the scripts underbin/
- add a new scheduler addon entry using Heroku's web UI to each of prototype/stage/prod, making sure to prefix the command run with the new relic admin wrapper (see other such scheduler commands for examples), and pick an appropriate dyno size
- check the papertrail logs to ensure the command runs successfully (eg doesn't run out of memory on the chosen dyno size), using eg:
For an example of the in-repo changes required, see:
https://github.com/mozilla/treeherder/pull/4300
Comment 1•5 years ago
|
||
We don't have CELERYBEAT_SCHEDULE
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INVALID
Updated•5 years ago
|
Product: Tree Management → Tree Management Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•