starred/asynq

Fork 0

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. #260

New issue

Closed

opened 2026-03-02 05:20:00 +03:00 by kerem · 3 comments

kerem commented

2026-03-02 05:20:00 +03:00

Owner

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

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**

kerem

2026-03-02 05:20:00 +03:00

closed this issue
added the
enhancement
label

kerem commented

2026-03-02 05:20:01 +03:00

Author

Owner

@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.

@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.

kerem commented

2026-03-02 05:20:01 +03:00

Author

Owner

@hibiken commented on GitHub (Oct 1, 2022):

thanks @Lilihx for the question, and thanks @AMAN-BARBARIA for answering!

@hibiken commented on GitHub (Oct 1, 2022): thanks @Lilihx for the question, and thanks @AMAN-BARBARIA for answering!

kerem commented

2026-03-02 05:20:01 +03:00

Author

Owner

@XTeam-Wing commented on GitHub (Dec 1, 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.
But it conflicts with priority.

@XTeam-Wing commented on GitHub (Dec 1, 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. But it conflicts with priority.

kerem referenced this issue

2026-03-07 22:05:50 +03:00

[GH-ISSUE #260] [FEATURE REQUEST] Asynq logo #1110

kerem referenced this issue

2026-03-15 19:15:14 +03:00

[GH-ISSUE #260] [FEATURE REQUEST] Asynq logo #2121

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#260

No description provided.

Rows
Columns