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.
When the S3 service experiences service-issues, it can cause the auto-recovery enabling cron jobs to go out to lunch and pile up. Need to ensure that said cron-jobs don't run past their run widow (constrain to < 20 minutes or whatever RPO - 2m works out to).
Fix recommendation:
Encapsulate auto-recovery enabling cron-job in a timeout() block
The text was updated successfully, but these errors were encountered:
Problem Description:
When the S3 service experiences service-issues, it can cause the auto-recovery enabling cron jobs to go out to lunch and pile up. Need to ensure that said cron-jobs don't run past their run widow (constrain to < 20 minutes or whatever
RPO - 2m
works out to).Fix recommendation:
Encapsulate auto-recovery enabling cron-job in a
timeout()
blockThe text was updated successfully, but these errors were encountered: