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
It seems that if I continue to refresh /sidekiq/queues/high - I see a lot of change. And I took a look at the codez and it looks like the gem might work by:
letting sidekiq pluck jobs off the queue normally
re-enqueue them if the job should be throttled
...which would explain why my queue seems so volatile.
Is it possible to avoid this rotation and work the jobs in the order they were enqueued?
Hi. You're right, current version rotates the queue. Throttling happens on per-worker class, not queue. There's no way to overcome this right now. But I have this on my list of things to improve – a way to configure throttling on a per-queue basis.
It seems that if I continue to refresh
/sidekiq/queues/high
- I see a lot of change. And I took a look at the codez and it looks like the gem might work by:...which would explain why my queue seems so volatile.
Is it possible to avoid this rotation and work the jobs in the order they were enqueued?
Fwiw, I'm throttling multiple jobs with:
The text was updated successfully, but these errors were encountered: