mirror of
https://github.com/hibiken/asynq.git
synced 2026-04-26 15:35:55 +03:00
[GH-ISSUE #351] [FEATURE REQUEST] Rethink the semantics of "Paused" queue #1166
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#1166
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 @hibiken on GitHub (Nov 17, 2021).
Original GitHub issue: https://github.com/hibiken/asynq/issues/351
Originally assigned to: @hibiken on GitHub.
With current implementation (v0.19.0), the semantics of "paused" queue is such that no workers are going to pick up tasks from the queue (i.e. we stop tasks from the queue to be handled while the queue is paused).
This may be sufficient to stop bad task handlers to execute to bring down the error rate. However, we may also want to support "pausing the queue" from the client side, so that we block all clients to enqueue tasks to the queue. A possible use case would be to drain the queue, we want to stop all clients to send tasks to a queue so that we can let handlers to execute all the backlog tasks.
We should add a separate operation for this use case.