Following up on slack conversation. Idea is to implement methods to implement a "static queue" within redis and allow tasks to target that queue. So if you had situations that you wanted to, say, run a config backup job for 5000 devices, you could spin up a FIFO worker and "route" those 5000 jobs to that worker. Would allow for the "main" worker queue to take on other (possibly/likely higher priority) tasks.
Following up on slack conversation. Idea is to implement methods to implement a "static queue" within redis and allow tasks to target that queue. So if you had situations that you wanted to, say, run a config backup job for 5000 devices, you could spin up a FIFO worker and "route" those 5000 jobs to that worker. Would allow for the "main" worker queue to take on other (possibly/likely higher priority) tasks.