Stopping Jobs
Stop a job when you want to stop processing data for the pipeline included in the job.
When stopping a job, Control Hub waits for the pipeline to gracefully complete all tasks for the in-progress batch. In some situations, this can take several minutes.
For example, if a scripting processor includes code with a timed wait, Control Hub waits for the scripting processor to complete its task. Then, Control Hub waits for the rest of the pipeline to complete all tasks before stopping the pipeline.
When you stop a job that includes an origin that can be reset, Control Hub maintains the last-saved offset for the job. For more information, see Job Offsets.
- In the Navigation panel, click Jobs.
-
Select active jobs in the list, and then click the Stop
icon:
. Or when monitoring an active job, click the Stop
icon.
Tip: You can also stop a job from a topology. -
In the confirmation dialog box that appears, click
Yes.
Depending on the pipeline complexity, the job might take some time to stop.
When a job remains in a Deactivating state for an unexpectedly long period of time, you can force Control Hub to stop the job immediately.