Resource Thresholds
- CPU load
- Memory used (Data Collector 3.13.x and later)
- Number of running pipelines
When multiple matching Data Collectors have not exceeded their resource thresholds, Control Hub prioritizes Data Collectors that are currently running the fewest number of pipelines. For example, you start a job and two matching Data Collectors have the maximum CPU load set to 100%. Data Collector A is currently using 70% of the CPU and running 1 pipeline. Data Collector B is currently using 50% of the CPU and running 3 pipelines. Control Hub starts a pipeline instance for the job on Data Collector A.
JOBRUNNER_72 - Insufficient Data Collector resources to run job. All matching Data Collectors [<URLs>] have reached their maximum CPU usage limits.
When a matching Data Collector no longer exceeds its resource thresholds, Control Hub randomly assigns a job from the queue to that Data Collector, changing the job status to green active and running a pipeline instance on that Data Collector.
Defining Resource Thresholds
You can define the resource thresholds for any registered Data Collector.
- In the navigation panel, click .
- Expand the details for the Data Collector that you want to configure.
-
Configure the following threshold values:
Threshold Description Max CPU Load (%) Maximum percentage of CPU that can be used. Default is 100. Max Memory (%) Maximum percentage of memory that can be used. Default is 100. Monitored for Data Collector 3.13.x and later.
Max Running Pipeline Count Maximum number of pipelines that can be running. Default is 1,000,000. - Click Save.