Synchronizing Jobs
Synchronize a job when you've changed the labels assigned to Data Collectors or Edge Data Collectors and the job is actively running on those engines. Or, synchronize a job to trigger a restart of a non running pipeline that has encountered an error.
- Starts pipelines on additional Data Collectors or Edge Data Collectors that match the same labels as the job and that have not exceeded any resource thresholds.
- Stops pipelines on Data Collectors or Edge Data Collectors that no longer match the same labels as the job.
- Restarts non-running pipelines from the last-saved offset on the same Data Collector or Data Collector Edge that matches the same labels as the job and that has not exceeded any resource thresholds. For example, a pipeline might have stopped running after encountering an error or after being deleted from that Data Collector.
Control Hub does not perform any action on execution engines that have labels that still match the job labels and that are already running a pipeline for the job.
For example, let’s say a job is active on three Data Collectors with label Test. If you remove label Test from one of the Data Collectors, synchronize the active job so that the pipeline stops running on that Data Collector. Or, let's say that one of the three pipelines running for the job has encountered an error and has stopped running. If you synchronize the active job, Control Hub triggers a restart of the pipeline on that same Data Collector.