mirror of
https://github.com/hibiken/asynq.git
synced 2026-04-26 07:25:56 +03:00
[GH-ISSUE #395] [FEATURE REQUEST] Distributed Scheduler #1189
Labels
No labels
CLI
bug
designing
documentation
duplicate
enhancement
good first issue
good first issue
help wanted
idea
invalid
investigate
needs-more-info
performance
pr-welcome
pull-request
question
wontfix
work in progress
work in progress
work-around-available
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/asynq#1189
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @aakashbajaj on GitHub (Feb 3, 2022).
Original GitHub issue: https://github.com/hibiken/asynq/issues/395
Originally assigned to: @hibiken on GitHub.
Is your feature request related to a problem? Please describe.
RIght now, a dedicated scheduler needs to be running. If that instance/service goes down, there's no way of recovery (specifically in kubernetes pod)
Describe the solution you'd like
Multiple schedulers register themselves on redis and maintain a master copy of Scheduler Entries. So, that if one instance goes down, other can pick right back up from there.
@hibiken commented on GitHub (Feb 4, 2022):
@aakashbajaj Thank you for opening an issue!
Can you run a multiple instances of
PeriodicTaskManager(see wiki here for more details) and store the periodic task configuration in a durable storage (e.g. Database, file in a distrubted filesystem, etc) and source that withPeriodicTaskConfigProvider?To prevent these multiple instances of
PeriodicTaskManagers from enqueueing duplicate tasks, you should be able to use the combinations of the following task options.TaskID(uniqueID)Retention(duration)(This is kind of a workaround since the current
Uniqueoption doesn't work well if the task gets processed quickly, see the discussion below for details).This was previously discussed here in this discussion.
Let me know if you have more questions or feedback!
@aakashbajaj commented on GitHub (Feb 7, 2022):
Thanks @hibiken for the suggestion. I'll look into this.
@hibiken commented on GitHub (Feb 8, 2022):
@aakashbajaj Closing this for now, but feel free to open this with a follow-up question or feedback 👍