Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

High Availability? #271

Open
odie5533 opened this issue Mar 2, 2024 · 0 comments
Open

High Availability? #271

odie5533 opened this issue Mar 2, 2024 · 0 comments

Comments

@odie5533
Copy link

odie5533 commented Mar 2, 2024

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant