feat(db): write a periodic heartbeat to keep the database active - #17
Merged
Merged
Conversation
A new Celery beat task, database_heartbeat, rewrites the single row of a new heartbeat table (migration 0007, row level security on) every six hours, so the database always shows a recent write even on days when nobody signs in or uploads anything. Six hours rather than a day because the beat schedule restarts with the worker on every deploy.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
A new Celery beat task, database_heartbeat, rewrites the single row of a new heartbeat table (migration 0007, row level security on) every six hours, so the database always shows a recent write even on days when nobody signs in or uploads anything. Six hours rather than a day because the beat schedule restarts with the worker on every deploy.