use case

We have a process_class P with 5 tasks and 3 jobs:

• A: min_tasks=1, idle_timout=1000, tasks=4
• B: min_tasks=1, idle_timout=1000, tasks=4
• C: nothing special

4 tasks of A are running (and acutally processing).
1 task of B is being started (because of min_tasks=1).
Job C wants to start, so we get:

SCHEDULER-271 Task is being terminated in favour of job C

and a little bit later

Task B:123 ended immediately after start, so min_tasks=1 doesn't lead to new tasks

Why this should not be a warning

The user configured a lot of tasks but restricted them using a process class. He actually wants his tasks to be restricted.
In a heavy load situation JobScheduler recognizes that it can run another process when terminating an unused task. This is also what the user intended, so there is no reason to warn.

a different use case

It is a different situation, if B wants to start (because of min_tasks) but cannot start because spooler_init() returns false. In that case a warning is needed, because something in the job implementation is preventing the job from starting.