[
https://issues.apache.org/jira/browse/FLINK-12836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-12836:
-----------------------------------
Labels: auto-deprioritized-major auto-deprioritized-minor auto-unassigned
(was: auto-deprioritized-major auto-unassigned stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> Allow retained checkpoints to be persisted on success
> -----------------------------------------------------
>
> Key: FLINK-12836
> URL: https://issues.apache.org/jira/browse/FLINK-12836
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Checkpointing
> Reporter: Andrew Duffy
> Priority: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor,
> auto-unassigned
>
> Currently, retained checkpoints are persisted with one of 3 strategies:
> * {color:#333333}CHECKPOINT_NEVER_RETAINED:{color} Retained checkpoints are
> never persisted
> * {color:#333333}CHECKPOINT_RETAINED_ON_FAILURE:{color}{color:#333333}
> Latest retained checkpoint{color} is persisted in the face of job failures
> * {color:#333333}CHECKPOINT_RETAINED_ON_CANCELLATION{color}: Latest retained
> checkpoint is persisted when job is canceled externally (e.g. via the REST
> API)
>
> I'm proposing a third persistence mode: _CHECKPOINT_RETAINED_ALWAYS_. This
> mode would ensure that retained checkpoints are retained on successful
> completion of the job, and can be resumed from later.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
