Confirmed users
3,990
edits
ReleaseEngineering/BuildAPI: Difference between revisions
Jump to navigation
Jump to search
→report crontask
| Line 176: | Line 176: | ||
=== report crontask === | === report crontask === | ||
There's a crontask on relengwebadm that runs every minute to generate the builds-4hr.js file. If this crontask gets "hung", it will prevent updates from occuring. This can happen due to DB connection issues, or bad data in the DB. In these cases, killing the hung crontask is the appropriate fix. | There's a crontask on [https://mana.mozilla.org/wiki/display/websites/Releng+Cluster relengwebadm] that runs every minute to generate the builds-4hr.js file. If this crontask gets "hung", it will prevent updates from occuring. This can happen due to DB connection issues, or bad data in the DB. In these cases, killing the hung crontask is the appropriate fix. | ||
However, the crontask takes about 15 minutes to run on a cold cache. So if its cache (memcached) has gone cold, then killing it before 15 minutes have elapsed is only delaying the failure. | However, the crontask takes about 15 minutes to run on a cold cache. So if its cache (memcached) has gone cold, then killing it before 15 minutes have elapsed is only delaying the failure. | ||
You can also read [https://bugzilla.mozilla.org/show_bug.cgi?id=1005342#c6 this comment]. | |||
= Staging = | = Staging = | ||