mirror of
https://github.com/hibiken/asynq.git
synced 2026-04-26 07:25:56 +03:00
[GH-ISSUE #551] [FEATURE REQUEST] The msg cannot be consumed by my expected worker. #1276
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#1276
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 @Lilihx on GitHub (Sep 29, 2022).
Original GitHub issue: https://github.com/hibiken/asynq/issues/551
Originally assigned to: @hibiken on GitHub.
Is your feature request related to a problem? Please describe.
In our debug mod, we share a redis. So there are several workers, and I want to make breakpoints in my IDE.
In this situation, how can i ensure that the msg sent from my local producer was consumed by my local worker ?
Describe the solution you'd like
I do not know if there is any option now.
Describe alternatives you've considered
Additional context
@AMAN-BARBARIA commented on GitHub (Sep 30, 2022):
@Lilihx One way of achieving that could be to add prefix to the queue names.So each worker subscribes to different queue based on what prefix you set and then the producers can enqueue in specific queue?
We too share a common redis server for our local development and each developer use a different prefix set in the environment variable so the queue is different and messages are sent/consumed by the expected workers only.
@hibiken commented on GitHub (Oct 1, 2022):
thanks @Lilihx for the question, and thanks @AMAN-BARBARIA for answering!
@XTeam-Wing commented on GitHub (Dec 1, 2022):