Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
For DD based jobs the scaleout is not based on process_pipeline_count specified in job's spec. Instead, the code tries to fetch the scaleout from a DD which is not right.
When a job is submitted, the OR creates a command line to launch a JP to run the job. The OR takes the value of process_pipeline_count parameter and creates a System property from it as follows:
arg[4]: -Dducc.deploy.JpThreadCount=2
All the JP needs to do is to fetch the property value and use it to create matching number of process threads that will request WIs from a JD.