If a job has to wait for a free process class, we get
SCHEDULER-949 Job will be executed when a process of process class '' becomes available
JobScheduler will then end an idle task (if available) of the process class to make room for the new job.
Reading the logs, I get the impression, that JobScheduler ends more tasks than necessary:
- In line 23 a Job wants to start, but waits for a process
- three tasks are then being terminated in lines 24, 25, 29
Only 1 task should be terminated in this case.
Jobs without min_tasks should be preferred for termination over tasks with min_tasks>0.