Page History
If you need to abort a running Job then the best approach is to 'Kill' the Flow in Azkaban, which in turn will update the job status in RED thus keeping the two systems in sync.
Navigate to the running Flow Execution and click the 'Kill' button to stop the current execution and synchronize the job status in RED.
Aborting a job from the RED UI is possible from RED 10.5+ but this action does not synchronize the related Azkaban execution so should really only be used when your Azkaban execution has finished but RED UI is showing it as still running.
A job can be aborted by right-clicking the job in the RED Scheduler window and choosing Abort Job from the context menu.
Once in this state, a job cannot be restarted. The job now only exists as a log of what occurred and is no longer regarded as a job.
...
The effects of aborting a job depend on the Operating System the Scheduler is running on, the target platform, and the action being run.
| Note |
|---|
Rolling back the current transaction may take a considerable amount of time. |
...
Greenplum (target)
Load and update processes are not stopped for all objects.
Hive (target)
Load and update processes are not stopped for all objects.
Netezza (target)
Load and update processes are not stopped for all objects.
PDW (target)
Object | Action | Effect |
|---|---|---|
Load | Native Load, SSIS Load | Does not stop process |
Load | ODBC Load, Database Link Load, File/Script Windows Load | Stops process |
All objects using Procedures (Local targets) | Update | Stops process and rolls back current transaction |
All objects using Procedures (remote targets) | Update | Does not stop process |
Cube | Update | Does not stop process |
...
Hive (target)
File/Hadoop Load processes are not stopped on Hive target platforms.