[jira] [Updated] (FLINK-18263) Allow external checkpoints to be persisted even when the job is in "Finished" state.

["Flink Jira Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLINK-18263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Flink Jira Bot updated FLINK-18263:
-----------------------------------
    Labels: auto-deprioritized-major pull-request-available stale-minor  (was: auto-deprioritized-major pull-request-available)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Minor but is unassigned and neither itself nor its Sub-Tasks have been updated for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is still Minor, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized.


> Allow external checkpoints to be persisted even when the job is in "Finished" state.
> ------------------------------------------------------------------------------------
>
>                 Key: FLINK-18263
>                 URL: https://issues.apache.org/jira/browse/FLINK-18263
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Checkpointing
>            Reporter: Mark Cho
>            Priority: Minor
>              Labels: auto-deprioritized-major, pull-request-available, stale-minor
>
> Currently, `execution.checkpointing.externalized-checkpoint-retention` configuration supports two options:
> - `DELETE_ON_CANCELLATION` which keeps the externalized checkpoints in FAILED and SUSPENDED state.
> - `RETAIN_ON_CANCELLATION` which keeps the externalized checkpoints in FAILED, SUSPENDED, and CANCELED state.
> This gives us control over the retention of externalized checkpoints in all terminal state of a job, except for the FINISHED state.
> If the job ends up in "FINISHED" state, externalized checkpoints will be automatically cleaned up and there currently is no config that will ensure that these externalized checkpoints to be persisted.
> I found an old Jira ticket FLINK-4512 where this was discussed. I think it would be helpful to have a config that can control the retention policy for FINISHED state as well.
> - This can be useful for cases where we want to rewind a job (that reached the FINISHED state) to a previous checkpoint.
> - When we use externalized checkpoints, we want to fully delegate the checkpoint clean-up to an external process in all job states (without cherrypicking FINISHED state to be cleaned up by Flink).
> We have a quick fix working in our fork where we've changed `ExternalizedCheckpointCleanup` enum:
> {code:java}
> RETAIN_ON_FAILURE (renamed from DELETE_ON_CANCELLATION; retains on FAILED)
> RETAIN_ON_CANCELLATION (kept the same; retains on FAILED, CANCELED)
> RETAIN_ON_SUCCESS (added; retains on FAILED, CANCELED, FINISHED)
> {code}
> Since this change requires changes to multiple components (e.g. config values, REST API, Web UI, etc), I wanted to get the community's thoughts before I invest more time in my quick fix PR (which currently only contains minimal change to get this working).



--
This message was sent by Atlassian Jira
(v8.20.1#820001)