Details
-
Fix
-
Status: Dismissed (View Workflow)
-
Minor
-
Resolution: Works as designed
-
1.12
-
None
Description
Current Situation
When a job has the attribute idletime=0 and there is one running order and one order waiting for task then the second order will run in the same task as the first order.
Desired Behavior
When a job has the attribute idletime=0 and there is one running order and one order waiting for task then the second order should run in a new task. For each order a new task should be created.
Maintainer Notes
This issue is dismissed as the intended behavior with idle_timeout="0" is different:
- The task will be re-used after execution of the current order should any additional order be waiting in front of the current job node.
- The task will be terminated should no additional orders be waiting for the current job node.