Tweak Check Schedule #222
Tweak Check Schedule #222
Conversation
| @@ -756,7 +756,7 @@ | |||
| "title": "Process Download Tracking Items", | |||
| "group": "System checks", | |||
| "schedule": { | |||
| "hourly_checks": { | |||
| "ten_min_checks": { | |||
There was a problem hiding this comment.
So this is just trying to keep up with the pace? Too bad there's not a comment field in this format.
There was a problem hiding this comment.
Correct. If we want to keep this we need it running very regularly as we can only purge ~100 or so every run. If we do it every hour we will only delete ~2400 and on Cloudwatch I see tens of thousands being generated overnight. This change will allow us to at least purge ~15000 or so a day, which should help us keep up.
| @@ -110,7 +110,7 @@ | |||
| "title": "Change in item counts", | |||
| "group": "Metadata checks", | |||
| "schedule": { | |||
| "morning_checks": { | |||
| "morning_checks_2": { | |||
There was a problem hiding this comment.
Why this rename? Is this just a name or something semantic?
There was a problem hiding this comment.
morning_checks_2 is actually a separate, unused schedule that is staggered from the regular morning_checks. You can see the schedule in app.py.
purge_download_tracking_itemsto no longer bail when staging deploy is runningchange_in_item_countsto run on the secondary morning check schedule