Hi Wu, The basic idea of checkpoints is that they are fully managed by Flink and only used for fault tolerance. Hence, if a job is stopped, there should not be any checkpoint lingering around. Savepoints on the other hand or snapshots that are managed by the user, and can be used to start a new job.
So in your case, it would be best to use savepoints by invoking "stop with savepoint". I can give you more details if you want. Please let me know if savepoints are not an option for you. On Sat, Apr 2, 2022 at 12:30 PM Wu Poker <pokerwu1...@gmail.com> wrote: > Dear Flinkers: > As "CheckpointProperties#CHECKPOINT_RETAINED_ON_CANCELLATION" shows, > if Job stopped with JobStatus#FINISHED "CompletedCheckpointStore" will > discard all completed checkpoints. > My question is, why job on the FINISHED status the > CompletedCheckpointStore discard all completed checkpoints. What will > happen if the completed checkpoint remains? > > In my case: in Flink version 1.14.4 use StreamGraph to execute the > bound source and remain checkpoints for the next crontab trigger. Is that > possible? (Change CheckpointProperties to remain all checkpoints on the job > FINISHED) > > Sincerely. >
