[GH-ISSUE #856] [FEATURE REQUEST] Support dynamic queue #2443

Open
opened 2026-03-15 20:31:50 +03:00 by kerem · 4 comments
Owner

Originally created by @yangzhiw on GitHub (Apr 8, 2024).
Original GitHub issue: https://github.com/hibiken/asynq/issues/856

Originally assigned to: @hibiken on GitHub.

Is your feature request related to a problem? Please describe.
My usage scenario is that I want to put different businesses into different queues. Businesses change dynamically. When the program is running, it supports putting different data into different queues, and different queues support different threads. consumption.

Originally created by @yangzhiw on GitHub (Apr 8, 2024). Original GitHub issue: https://github.com/hibiken/asynq/issues/856 Originally assigned to: @hibiken on GitHub. **Is your feature request related to a problem? Please describe.** My usage scenario is that I want to put different businesses into different queues. Businesses change dynamically. When the program is running, it supports putting different data into different queues, and different queues support different threads. consumption.
Author
Owner

@kamikazechaser commented on GitHub (Apr 8, 2024):

Related to #850, #852

<!-- gh-comment-id:2041820749 --> @kamikazechaser commented on GitHub (Apr 8, 2024): Related to #850, #852
Author
Owner

@yangzhiw commented on GitHub (Apr 9, 2024):

Thank you. Another inquiry: Different queues use different coroutines to consume, and queue-level concurrency is supported; because looking at the source code now, it seems that there is only one processor to pull data.

<!-- gh-comment-id:2044039428 --> @yangzhiw commented on GitHub (Apr 9, 2024): Thank you. Another inquiry: Different queues use different coroutines to consume, and queue-level concurrency is supported; because looking at the source code now, it seems that there is only one processor to pull data.
Author
Owner

@kamikazechaser commented on GitHub (Apr 9, 2024):

That is also being addressed in #849

<!-- gh-comment-id:2044109454 --> @kamikazechaser commented on GitHub (Apr 9, 2024): That is also being addressed in #849
Author
Owner

@gsaraf commented on GitHub (Jan 16, 2025):

Hi! I'm looking at a similar requirement, and would be interested in extending this feature to make the queue update more "on-the-fly". So instead of shutting down the server and bringing it back up with the new configuraiton, we would update the required configurations where needed.

I don't think it is blocking the current implementation in #879. Would there be interest in an improvement on top?

<!-- gh-comment-id:2595703958 --> @gsaraf commented on GitHub (Jan 16, 2025): Hi! I'm looking at a similar requirement, and would be interested in extending this feature to make the queue update more "on-the-fly". So instead of shutting down the server and bringing it back up with the new configuraiton, we would update the required configurations where needed. I don't think it is blocking the current implementation in #879. Would there be interest in an improvement on top?
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/asynq#2443
No description provided.