Details
-
Bug
-
Status: Resolved
-
Critical
-
Resolution: Fixed
-
None
-
None
Description
Currently in IterativeWorkflowProcessorThread, this code block automatically sets Load Value to 2 and doesn't allow override:
if (rClient != null) { // build up the Job // and the Job Input Job taskJob = new Job(); taskJob.setName(task.getTaskId()); taskJob .setJobInstanceClassName("org.apache.oodt.cas.workflow.structs.TaskJob"); taskJob .setJobInputClassName("org.apache.oodt.cas.workflow.structs.TaskJobInput"); taskJob.setLoadValue(new Integer(2)); taskJob .setQueueName(task.getTaskConfig().getProperty(QUEUE_NAME) != null ? task .getTaskConfig().getProperty(QUEUE_NAME) : DEFAULT_QUEUE_NAME);
I could have sworn this was configurable before, but I guess it wasn't. I'm going to add a property called "Load" that can be set in tasks.xml on a per WorkflowTask basis, that will propagate and allow override of the resource manager job load when workflow manager is connecting to the resource manager.