mirror of
https://github.com/hibiken/asynq.git
synced 2026-04-26 07:25:56 +03:00
[GH-ISSUE #688] [FEATURE REQUEST] when stopping asynq encounters a task that exceeds ShutdownTime, can the user determine whether to put it back into the queue #1357
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#1357
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 @jiangbo202 on GitHub (Jul 20, 2023).
Original GitHub issue: https://github.com/hibiken/asynq/issues/688
Originally assigned to: @hibiken on GitHub.
I want to discard the tasks that are not closed when the timeout expires when I stop the asynq task, which means that the task will not be restarted when it is started next time.
So whether it can be made configurable, some tasks will be put back into the queue when they are closed and timed out, and some tasks will not be put back into the queue when they are closed and timed out.
I don't know if this idea is reasonable, just offering my thoughts
@hibiken commented on GitHub (Jul 22, 2023):
@jiangbo202 Would you mind explaining what you mean by "Closing" a task?
When processing exceeds the deadline, the task should be back in the queue for retry.