flink-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Metzger <rmetz...@apache.org>
Subject Re: Diff between stop and cancel job
Date Thu, 05 May 2016 11:30:31 GMT
Hi Abhi,

The difference between cancelling and stopping a (streaming) job is the

On a cancel call, the operators in a job immediately receive a `cancel()`
method call to cancel them as
soon as possible.
If operators are not not stopping after the cancel call, Flink will start
interrupting the thread periodically
until it stops.

A "stop" call is a more graceful way of stopping a running streaming job.
Stop is only available for jobs
which use sources that implement the `StoppableFunction` interface. When
the user requests to stop a job,
all sources will receive a `stop()` method call. The job will keep running
until all sources properly shut down.
This allows the job to finish processing all inflight data.

In order to resume a job, you need to create a savepoint first. You can
then stop or cancel the job and resume from the savepoint.


On Thu, May 5, 2016 at 1:59 AM, Bajaj, Abhinav <abhinav.bajaj@here.com>

> Hi,
> Can some one please clarify the difference between stop and cancel of a
> Job.
> Stop documentation mentions it is only for "streaming jobs only” but
> cancel also works for it.
> Or can we resume a stopped streaming job ?
> Thanks,
> Abhi
> *[image: cid:DACBF116-FD8C-48DB-B91D-D54510B306E8]*
> *Abhinav Bajaj*
> Senior Engineer
> HERE Predictive Analytics
> Office:  +12062092767
> Mobile: +17083299516
> *HERE Seattle*
> 701 Pike Street, #2000, Seattle, WA 98101, USA
> *47° 36' 41" N. 122° 19' 57" W*
> *HERE Maps*

View raw message