ReleaseEngineering/How To/Restart Redis: Difference between revisions

Jump to navigation Jump to search
m
Line 11: Line 11:
{{Bug|905587}} tracks an issue with the version we're running where it stops functioning after opening too many file descriptors. This results in [https://secure.pub.build.mozilla.org/builddata/buildjson/builds-4hr.js.gz builds-4hr.js.gz] getting stale, and TBPL stops getting information about builds that are recently finished. This is a tree closing problem.
{{Bug|905587}} tracks an issue with the version we're running where it stops functioning after opening too many file descriptors. This results in [https://secure.pub.build.mozilla.org/builddata/buildjson/builds-4hr.js.gz builds-4hr.js.gz] getting stale, and TBPL stops getting information about builds that are recently finished. This is a tree closing problem.


We disabled the cronjobs since the unattended restart could leave things in a bad state. Buildduty manually restarts the service and rail added some monit monitoring.
NOTE: We disabled the cronjobs since the unattended restart could leave things in a bad state. Buildduty manually restarts the service and rail added some monit monitoring. <br />
<strike>
<strike>
''Note: as of 2013-10-18 there are cronjobs on redis01 that attempt to automatically do the fix below. See {{bug|905587}} for details.''
''Note: as of 2013-10-18 there are cronjobs on redis01 that attempt to automatically do the fix below. See {{bug|905587}} for details.''
Confirmed users
3,990

edits

Navigation menu