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
Let's assume I cancel the "asynq.server" and the "asynq.client" manually by stopping the execution of my program via console. As a consequence the tasks that can not be finished in time are pushed back to the queue. Is pushing a task back to the queue considered as a retry that matters to the tasks' "MaxRetry" option?
I've used "MaxRetry()" to create a retryOption and passed it to "NewTask()" when creating a new task. Even so I've set the number of retries to zero the tasks still get pushed back to the queue and are restarted when starting the program again.
So either I've got some bugs in my code or I'am misunderstanding what is considered as a retry and what is not:-)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hey!
Let's assume I cancel the "asynq.server" and the "asynq.client" manually by stopping the execution of my program via console. As a consequence the tasks that can not be finished in time are pushed back to the queue. Is pushing a task back to the queue considered as a retry that matters to the tasks' "MaxRetry" option?
I've used "MaxRetry()" to create a retryOption and passed it to "NewTask()" when creating a new task. Even so I've set the number of retries to zero the tasks still get pushed back to the queue and are restarted when starting the program again.
So either I've got some bugs in my code or I'am misunderstanding what is considered as a retry and what is not:-)
I would be glad about any help:-)
Beta Was this translation helpful? Give feedback.
All reactions