Each Data Mover job that is currently running has an effect on the ability to run other jobs. A Data Mover job has one or more tasks that an agent can perform using Teradata JDBC, DSA, QueryGrid, or Teradata PT API. As the number of concurrent jobs increases, the number of tasks increases, resulting in competition for resources of the agent. To avoid a bottleneck, Data Mover limits the number of jobs that can run concurrently. After the limit is reached, all new job execution requests are queued and run when other jobs complete.
By default, the concurrent task limit is set to 20. Depending on the types of jobs being run and the number of Data Mover agents available, this limit could be too low or too high. You may want to change it. You can also use flexible scheduling to improve performance by setting different limits for different time periods during the day.
- Set the value for the jobExecutionCoordinator.maxConcurrentJobs parameter in the daemon.properties file to the desired limit.This property is updated dynamically. The settings you provide take effect one minute after you save daemon.properties. The daemon does not need to be restarted.