Comparing Balance Jobs and Synchronize Jobs

Balancing Data Collector jobs differs from synchronizing jobs. The following table lists the key differences:

Action Description
Balance Jobs
  • Balance a job to redistribute the pipeline load for a job enabled for failover.
  • Only jobs enabled for pipeline failover and that are running on a Data Collector can be balanced.
  • When you balance a job, Control Hub performs the following actions:
    • Automatically determines if the pipeline load is evenly distributed across available Data Collectors that have not exceeded any resource thresholds.

      If the pipeline load is evenly distributed, Control Hub does not continue with the remaining actions.

      If the pipeline load is not evenly distributed - meaning that an available Data Collector not currently running a pipeline instance for the job is running fewer pipelines than another Data Collector currently running a pipeline instance for the job - then Control Hub continues with the remaining actions.

    • Stops a running pipeline instance for the job on one or more Data Collectors.
    • Restarts the pipeline from the last-saved offset on a matching number of available Data Collectors that have not exceeded any resource thresholds.
Synchronize Jobs
  • Synchronize a job when you've changed the labels assigned to execution engines and the job is actively running on those engines.
  • Any job can be synchronized.
  • When you synchronize a job, Control Hub performs the following actions:
    • 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.