ISD job priority and WLM queues
Posted: Thu Jan 28, 2016 1:29 pm
According to the Ops Console's Workload Management tab, by default there are 3 batch queues for jobs (Low, Medium, and High), and dedicated queues for ISD, IA, and DataClick.
Today we have deployed a new ISD application that is based on a DataStage job, and instead of running, it was Queued in the ISD queue. This seems to have happened because several IA tasks were already running and CPU usage was too high, and there was a very long wait for IA tasks to finish and reduce CPU to below the global threshold of 80%.
Are there any options to give ISD priority over IA, or over anything else for that matter?
Today we have deployed a new ISD application that is based on a DataStage job, and instead of running, it was Queued in the ISD queue. This seems to have happened because several IA tasks were already running and CPU usage was too high, and there was a very long wait for IA tasks to finish and reduce CPU to below the global threshold of 80%.
Are there any options to give ISD priority over IA, or over anything else for that matter?