We have a job we only want to run 1 at a time. For this we use DisableConcurrentExecution. Some times we create many of these jobs. the problem is these jobs make take a couple minutes to run and it can takes all the workers available while they wait for each other to finish. Is there a way to stop this from happening? It seem like a worker shouldn’t even pull those in for processing because while those are stuck waiting there are higher priority queues that fill up while the workers are waiting. Is there any way around this?
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Multiple queues with concurrent job limits | 0 | 1309 | July 20, 2017 | |
| Allowing for parallel processing only of specified jobs | 1 | 117 | September 26, 2024 | |
| Serial sequential queue? | 0 | 1659 | September 24, 2016 | |
| DisableConcurentExecution for Job Groups | 8 | 5474 | July 10, 2017 | |
| DisableConcurrentExecution Bug | 3 | 4069 | April 21, 2015 |