Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Different queues with one job per worker #2023

Closed
wazirsoft opened this issue Apr 26, 2021 · 0 comments
Closed

Different queues with one job per worker #2023

wazirsoft opened this issue Apr 26, 2021 · 0 comments

Comments

@wazirsoft
Copy link

I am having four different queues listening and running separate operations as typical queues do. Currently if each queue get one job all these four jobs would start processing at once and just on a single worker. I don't want to do this as each queue is resource intensive.

I can't merge all these four jobs into single queue to fix this concurrency issue. The reason is, I am using Arena and would like to see all the jobs separated by the queues like Arena let you see.

Do I have any other approach I can take to solve this problem?

@manast manast closed this as completed Apr 26, 2021
@OptimalBits OptimalBits locked and limited conversation to collaborators Apr 26, 2021

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants