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
I have several Queue Worker configurations configured in my Horizon config. fast, default and slow jobs. Each, with different queues specified in the queue array.
My slow jobs are my most important, and typically I have a lot of jobs on my uptime queue, thus why this is closer to the start.
I wanted to have a reserve "min processes" of 10 allocated here and a maximum of 55 so it can scale correctly. However, what ended up happening is it give a minimum of 10 to each queue defined in the array:
10 for on-demand-runs-now
9 for uptime
10 for domains
10 for blacklists
etc...
And uptime never went above 9. What's going on here? I need the queues to process in order, and for their to be a higher priority for processes to be allocated to uptime.
Can you first please try one of the support channels below? If you can actually identify this as a bug, feel free to open up a new issue with a link to the original one and we'll gladly help you out.
Horizon Version
5.21.4
Laravel Version
10.34.2
PHP Version
8.1.26
Redis Driver
PhpRedis
Redis Version
7.x
Database Driver & Version
Maria DB
Description
I have several Queue Worker configurations configured in my Horizon config.
fast
,default
andslow
jobs. Each, with different queues specified in thequeue
array.My
slow
jobs are my most important, and typically I have a lot of jobs on myuptime
queue, thus why this is closer to the start.I wanted to have a reserve "min processes" of 10 allocated here and a maximum of 55 so it can scale correctly. However, what ended up happening is it give a minimum of 10 to each queue defined in the array:
etc...
And
uptime
never went above 9. What's going on here? I need the queues to process in order, and for their to be a higher priority for processes to be allocated touptime
.Steps To Reproduce
My config I tried:
The text was updated successfully, but these errors were encountered: