Details
-
Feature
-
Status: Released (View Workflow)
-
Minor
-
Resolution: Fixed
-
1.9.11, 1.10.8, 1.11.4
-
None
Description
Current Situation
- The JITL jobs JobChainStart and JobChainEnd are dummy jobs used as start and end node.
- The JITL jobs has script language as Shell and has a Java configuration monitor sos.scheduler.managed.configuration.ConfigurationOrderMonitor. Due to fact that shell script has a Java configuration monitor, JVM is created and destroyed for every execution of shell script.
- For this jobs default max_task is 1, when these jobs are used across many job chains or in a high volume job chain, due to repeated JVM creation, jobs create a bottleneck effect.
Desired Situation
- job sos/jitl/JobChainStart
- script language="java:javascript" instead of shell
- idle_timeout="30" instead of default 5 seconds
- tasks="3" instead of default 1
- job sos/jitl/JobChainEnd
- remove the java configuration monitor
- Performance should be improved for high volume processing.
Attachments
Issue Links
There are no Sub-Tasks for this issue.