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
Hi. I'm looking at a simple situation: a periodic Task that runs once every 15 minutes. What ways will Redbeat guarantee the task runs every 15 minutes, and what ways will it fail? Will it be retried?
I'm thinking of having two replicas of Redbeat running, one as a backup. If the primary fails right before the Task would be scheduled, will the Task not get scheduled since the backup instance will take a moment to take over?
My other thought on handling this would be to put locks on the consumer side, so let multiple copies of regular Celery Beat run, creating duplicate tasks, and then handle de-duplication within the Task (with locks and unique names or something). What factors should I consider when deciding between these methods?
The text was updated successfully, but these errors were encountered:
Hi. I'm looking at a simple situation: a periodic Task that runs once every 15 minutes. What ways will Redbeat guarantee the task runs every 15 minutes, and what ways will it fail? Will it be retried?
I'm thinking of having two replicas of Redbeat running, one as a backup. If the primary fails right before the Task would be scheduled, will the Task not get scheduled since the backup instance will take a moment to take over?
My other thought on handling this would be to put locks on the consumer side, so let multiple copies of regular Celery Beat run, creating duplicate tasks, and then handle de-duplication within the Task (with locks and unique names or something). What factors should I consider when deciding between these methods?
The text was updated successfully, but these errors were encountered: