Start data refreshes on Mondays UTC 00:00 #3054
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes
Description
Starts the data refreshes on Mondays at UTC 0:00 instead of Tuesdays. This allows them to complete by Wednesday so that they will not block catalog deployments.
Note: we don't expect issues with the data refreshes running at the same time as popularity refreshes, but if we ever do observe any performance issues here we should shift the schedule of the popularity refresh, not the data refresh. The popularity refreshes are resilient to failure and don't have to complete before deployments can be run.
Testing Instructions
Run
just up
and check the audio and image data refreshes in the Airflow UI to verify that their schedules look correct.Checklist
Update index.md
).main
) or a parent feature branch.Developer Certificate of Origin
Developer Certificate of Origin