mirror of
https://github.com/hibiken/asynq.git
synced 2026-04-26 15:35:55 +03:00
[GH-ISSUE #241] [FEATURE REQUEST] Redis key prefix #85
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#85
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 @hellish on GitHub (Feb 6, 2021).
Original GitHub issue: https://github.com/hibiken/asynq/issues/241
Originally assigned to: @hibiken on GitHub.
Is your feature request related to a problem? Please describe.
no
Describe the solution you'd like
I want to be able to specify a prefix for all redis keys and pub sub channels used in this library. right now everything resides in asynq.* namespace but with a prefix it will be myapp.asynq.*
@hibiken commented on GitHub (Feb 7, 2021):
@hellish Thank you for opening this issue!
Would you mind explaining the reason you need this feature in detail, so that I can understand the use case.
It shouldn't be too difficult to add this feature, but I'm not 100% convinced that we need to support this.
@hibiken commented on GitHub (Mar 11, 2021):
Closing this for now. @hellish feel free to reopen the issue if this is still something that you're interested in.
@zdraganov commented on GitHub (Sep 3, 2021):
In detail, you can use the same Redis instance for multiple services that are running asynq. If so, we want to have separate redis entries for each of the service, so we can have
payment_asynq:...,order_asynq:...as any of those will be in the scope of the service itself.@hibiken commented on GitHub (Sep 5, 2021):
@zdraganov thank you for the comment.
Can we achieve that with custom queue names?
For example, you can create payment related queues such as
"payment:foo","payment:bar", etcand create order related queues such as
"order:baz","order:qux", etc.@gurupras commented on GitHub (Nov 5, 2022):
One neat way in which a prefix would help is to be able to host multiple isolated asynq-based worker pools within one redis server.