starred/asynq

Fork 0

mirror of https://github.com/hibiken/asynq.git synced 2026-04-26 15:35:55 +03:00

[GH-ISSUE #653] How to prevent duplicate scheduler task registe across multiple Asynq server nodes #323

New issue

Closed

opened 2026-03-02 05:20:28 +03:00 by kerem · 5 comments

kerem commented

2026-03-02 05:20:28 +03:00

Owner

Originally created by @wwwfeng on GitHub (May 4, 2023).
Original GitHub issue: https://github.com/hibiken/asynq/issues/653

How to prevent duplicate scheduler task registe across multiple Asynq server nodes

Originally created by @wwwfeng on GitHub (May 4, 2023). Original GitHub issue: https://github.com/hibiken/asynq/issues/653 How to prevent duplicate scheduler task registe across multiple Asynq server nodes

kerem closed this issue

2026-03-02 05:20:28 +03:00

kerem commented

2026-03-02 05:20:29 +03:00

Author

Owner

@wwwfeng commented on GitHub (May 4, 2023):

I have the following code, but if multiple instances of asynq are started, the scheduled task may be registered to Redis repeatedly. How to avoid this?

....
task := asynq.NewTask(pb.SchedulerType_STAT_CAR_UPTIME.String(), nil)
entryID, err := l.svcCtx.Scheduler.Register(crontab, task)
....

@wwwfeng commented on GitHub (May 4, 2023): I have the following code, but if multiple instances of asynq are started, the scheduled task may be registered to Redis repeatedly. How to avoid this? ``` .... task := asynq.NewTask(pb.SchedulerType_STAT_CAR_UPTIME.String(), nil) entryID, err := l.svcCtx.Scheduler.Register(crontab, task) .... ```

kerem commented

2026-03-02 05:20:29 +03:00

Author

Owner

@aaps3579 commented on GitHub (May 8, 2023):

@wwwfeng Yes. If multiple instances of scheduler are started, task will be scheduled multiple times.
Refer to this thread https://github.com/hibiken/asynq/issues/395 for solution.

@aaps3579 commented on GitHub (May 8, 2023): @wwwfeng Yes. If multiple instances of scheduler are started, task will be scheduled multiple times. Refer to this thread https://github.com/hibiken/asynq/issues/395 for solution.

kerem commented

2026-03-02 05:20:29 +03:00

Author

Owner

@wwwfeng commented on GitHub (May 8, 2023):

@wwwfeng Yes. If multiple instances of scheduler are started, task will be scheduled multiple times. Refer to this thread #395 for solution.

Thanks for your reply. I checked the documentation and used asynq.TaskID and asynq.Retention, and it seems to be effective. Does this mean that the same scheduled task will only be written once within the time set by asynq.Retention?

@wwwfeng commented on GitHub (May 8, 2023): > @wwwfeng Yes. If multiple instances of scheduler are started, task will be scheduled multiple times. Refer to this thread #395 for solution. Thanks for your reply. I checked the documentation and used ` asynq.TaskID` and ` asynq.Retention`, and it seems to be effective. Does this mean that the same scheduled task will only be written once within the time set by asynq.Retention?

kerem commented

2026-03-02 05:20:29 +03:00

Author

Owner

@aaps3579 commented on GitHub (May 8, 2023):

Retention time dictates for how much long task is gonna stay in the system. And any task enqueued with same taskID will give asynq.ErrTaskIDConflict error.

@aaps3579 commented on GitHub (May 8, 2023): Retention time dictates for how much long task is gonna stay in the system. And any task enqueued with same taskID will give asynq.ErrTaskIDConflict error.

kerem commented

2026-03-02 05:20:29 +03:00

Author

Owner

@wwwfeng commented on GitHub (May 8, 2023):

Retention time dictates for how much long task is gonna stay in the system. And any task enqueued with same taskID will give asynq.ErrTaskIDConflict error.

Thank you so much for your response.I understand now.

@wwwfeng commented on GitHub (May 8, 2023): > Retention time dictates for how much long task is gonna stay in the system. And any task enqueued with same taskID will give asynq.ErrTaskIDConflict error. Thank you so much for your response.I understand now.

kerem referenced this issue

2026-03-02 06:05:17 +03:00

[PR #323] [MERGED] Update NewTask function to take Option as varargs #712

kerem referenced this issue

2026-03-07 22:12:49 +03:00

[PR #323] [MERGED] Update NewTask function to take Option as varargs #1721

kerem referenced this issue

2026-03-15 21:00:25 +03:00

[PR #323] [MERGED] Update NewTask function to take Option as varargs #2731