Hi Sudhansu,
the usual flow is that if you cancel a job, you have 2 choices:
- Either you want to later resume the job, then you use stop-with-savepoint
and resume from savepoint. That would allow you to upgrade the job or the
Flink version. However, taking a final savepoint takes some time.
- Or
Hi Arvid,
The flink document says,
"ExternalizedCheckpointCleanup.DELETE_ON_CANCELLATION: Delete the
checkpoint when the job is cancelled. The checkpoint state will only be
available if the job fails."
If I have to resume the program after cancellation, Do I have to use
ExternalizedCheckpointCl
The flink version we are using is 1.12.2
Thanks,
Sudhansu
On Tue, May 11, 2021 at 7:48 PM Chesnay Schepler wrote:
> Which Flink version are you using?
>
> On 5/11/2021 4:09 PM, sudhansu jena wrote:
> > Hi Team,
> >
> > We have recently enabled Check Pointing in our flink job using
> > FSStateB
Which Flink version are you using?
On 5/11/2021 4:09 PM, sudhansu jena wrote:
Hi Team,
We have recently enabled Check Pointing in our flink job using
FSStateBackend pointing to S3 bucket.
Below is the sample code for enabling the checkpointing for the job.
The query is each time we cancel t
Hi Sudhansu,
if you don't set RETAIN_ON_CANCELLATION, the folder should be cleaned up
automatically. If you explicitly want to retain the checkpoint, then there
is not much that Flink can do or I may have misunderstood you.
On Tue, May 11, 2021 at 4:09 PM sudhansu jena
wrote:
> Hi Team,
>
> We
Hi Team,
We have recently enabled Check Pointing in our flink job using
FSStateBackend pointing to S3 bucket.
Below is the sample code for enabling the checkpointing for the job. The
query is each time we cancel the job and restart from the flink dashboard,
a new folder is getting created along w
