You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Xingcan Cui (Jira)" <ji...@apache.org> on 2024/12/12 17:04:00 UTC

[jira] [Closed] (FLINK-36893) Support periodic full checkpoint

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

Xingcan Cui closed FLINK-36893.
-------------------------------
    Resolution: Won't Fix

> Support periodic full checkpoint
> --------------------------------
>
>                 Key: FLINK-36893
>                 URL: https://issues.apache.org/jira/browse/FLINK-36893
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Checkpointing
>            Reporter: Xingcan Cui
>            Priority: Minor
>
> We have a few Flink jobs running with incremental checkpoints. The S3 bucket used to store the checkpoint files has an s3.entropy.key set and is automatically cleaned up with a time-based life cycle rule. However, the rule occasionally removes some pretty old checkpoint files that are still referenced by the latest checkpoint and that will make the job unrecoverable. It would be good if Flink can provide a periodic full checkpoint option that allows the checkpoint files to be fully refreshed.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)