Limit processes per Subagent Cluster

Current Situation

• Users can limit the number of parallel processes by use of Resource Locks that can include any number of Job Instructions and other instructions.
• Users can limit the number of processes per Agent, see JS-2096.

Desired Behavior

• Users would like to limit the number of parallel processes for jobs per Subagent Cluster.
  • Processes include execution of Shell Jobs.
  • The Process Limit is applied to JVM Jobs (Java, JavaScript, JITL) too,. Such jobs are not consuming an OS process, however execution should be limited by the same setting.
  • The process limit applies to use of individual Job Instructions.
• Limit
  • If the limit of parallel jobs is exceeded then any further job starts are delayed until a process becomes available within the given limit.
  • In this situation orders are put to the WAITING state with the status information WAITING_FOR_PROCESS.
  • If the number of parallel processes falls below the process limit specified then the next job can start. The next job is the first job that previously was delayed when the process limit was hit.
• Scope
  • For an Agent Cluster the process limit can be configured for each Subagent Cluster individually to limit the number of overall processes executed in parallel with the Subagent Cluster. If a process limit for the Director Agent applies (JS-2096) then this can delay job starts in a Subagent Cluster if the Director Agent's process limit is hit though the Subagent Cluster's process limit is not exceeded.
• Configuration
  • The process limit is specified with the configuration of a Subagent Cluster that is created and updated from REST calls to the Controller.
  • If no process limit is specified at the given level then the number of parallel processes is unlimited.