You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I've encountered a problem with prioritized jobs that I can't figure out.
Let's say I have a queue full of many jobs waiting to be processed by the same worker in the same queue, all these jobs have a priority of 2.
When I add a new job to the queue with a non-specified priority (the highest priority possible if I've read the documentation correctly), it doesn't run immediately after the end of the process of a job with a priority of 2. Could you explain why this is?
Is there a connection with the concurrency settings of my worker? I didn't specify a concurrency when I created it.
// QueuenewQueue("test",{connection: { ... }})// WorkernewWorker("test",()=>{/* my processor code here */},{connection: { ... },lockDuration: 300000,maxStalledCount: 3,stalledInterval: 60000,})
Should I just upgrade to bullMQ 4/5.X.X ?
Thanks in advance.
How to reproduce.
No response
Relevant log output
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
A job without priority should process before jobs with priorities. I do not know if there is something specific with your code that breaks this behaviour or a bug in your version of BullMQ. You should definitely upgrade as newer versions have a much better implementation of prioritised jobs, however if you have queues in production you may want to use new queues as your version is quite old and there may have incompatibilities with the newer ones.
Version
v3.5.6
Platform
NodeJS
What happened?
Hello, I've encountered a problem with prioritized jobs that I can't figure out.
Let's say I have a queue full of many jobs waiting to be processed by the same worker in the same queue, all these jobs have a priority of 2.
When I add a new job to the queue with a non-specified priority (the highest priority possible if I've read the documentation correctly), it doesn't run immediately after the end of the process of a job with a priority of 2. Could you explain why this is?
Is there a connection with the concurrency settings of my worker? I didn't specify a concurrency when I created it.
Should I just upgrade to bullMQ 4/5.X.X ?
Thanks in advance.
How to reproduce.
No response
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: