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 would be very valuable if you could queue items into queues with a priority, and have items pulled from the queue in priority order for processing by jobs.
I currently work around this by having multiple queues, with multiple jobs, but this means that multiple jobs are running simultaneously, which in some cases is not scalable due to resource constraints.
The text was updated successfully, but these errors were encountered:
That's really not possible with pretty much any queuing system. You end up having to do exactly what you are doing. Routing the messages to a dedicated high priority queue.
Would it be possible to give a job a list of queues (of the same type), so that it tried to pop off each of them, but only one would be able to get processed at any given time (because there is only one job task running)
It would be very valuable if you could queue items into queues with a priority, and have items pulled from the queue in priority order for processing by jobs.
I currently work around this by having multiple queues, with multiple jobs, but this means that multiple jobs are running simultaneously, which in some cases is not scalable due to resource constraints.
The text was updated successfully, but these errors were encountered: