Hi Henry,
Your understanding is correct. Checkpoint itself is for recovery purposes.
If you cancel a job, Flink thinks it doesn't make sense to save the
checkpoint again. If you want to recover after cancel, then you should use
cancel with savepoint. So, by default, you don't need to manually
Hi Vino,
So I will use the default setting of DELETE_ON_CANCELLATION. When the
program cancels the checkpoint will be deleted, when the program fails,because
the checkpoint will not be deleted, I still can have a checkpoint that can be
used to resume.
Please help to correct me
Hi Henry,
I gave a blue comment in your original email.
Thanks, vino.
徐涛 于2018年9月25日周二 下午12:56写道：
> Hi Vino,
> *What is the definition and difference between job cancel and job fails?*
> Can I say that if the program is shutdown artificially, then it is a job
> cancel,
>
Hi Vino,
What is the definition and difference between job cancel and job fails?
Can I say that if the program is shutdown artificially, then it is a
job cancel,
if the program is shutdown due to some error, it
is a job fail?
This is
Hi Henry,
Answer your question:
What is the definition and difference between job cancel and job fails?
> The cancellation and failure of the job will cause the job to enter the
termination state. But cancellation is artificially triggered and normally
terminated, while failure is usually a
Hi All,
I mean if I can guarantee that a savepoint can always be made before
manually cancelation. If I use DELETE_ON_CANCELLATION option on checkpoints, is
there any probability that I do not have a checkpoint to recover from?
Thank a a lot.
Best
Henry
> 在
Hi All,
In flink document, it says
DELETE_ON_CANCELLATION: “Delete the checkpoint when the job is
cancelled. The checkpoint state will only be available if the job fails.”
What is the definition and difference between job cancel and job fails?
If I run the program on
