You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 19, 2019. It is now read-only.
If AWS S3 experiences issues when writing backups, cronjobs pile up and crash the instance. To remedy this a timeout was added to the cronjob. However, if the cronjob times out backups are not written to S3.
Fix recommendation:
Create a lambda function to poll S3 and generate an alert if backups are not written at the required interval.
The text was updated successfully, but these errors were encountered:
This stopped being a problem for a few months, but has recently returned. Probably requires wholly rearchitecting the backups ...and possibly the storage used for ${JENKINS_HOME} (to allow for filesystem snapshotting to create a "static" backup-set to copy from).
Added an enhancement issue (#47) to describe a better backup system. While a monitoring lambda function would be useful, in general, the problem likely is best solved by a less-simplistic backup method.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Problem Description:
If AWS S3 experiences issues when writing backups, cronjobs pile up and crash the instance. To remedy this a timeout was added to the cronjob. However, if the cronjob times out backups are not written to S3.
Fix recommendation:
Create a lambda function to poll S3 and generate an alert if backups are not written at the required interval.
The text was updated successfully, but these errors were encountered: