[jira] [Assigned] (FLINK-17808) Rename checkpoint meta file to "_metadata" until it has completed writing

["Yun Tang (Jira)" <ji...@apache.org>]

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

Yun Tang reassigned FLINK-17808:
--------------------------------

    Assignee: Yun Tang

> Rename checkpoint meta file to "_metadata" until it has completed writing
> -------------------------------------------------------------------------
>
>                 Key: FLINK-17808
>                 URL: https://issues.apache.org/jira/browse/FLINK-17808
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Checkpointing
>    Affects Versions: 1.10.0
>            Reporter: Yun Tang
>            Assignee: Yun Tang
>            Priority: Major
>             Fix For: 1.12.0
>
>
> In practice, some developers or customers would use some strategy to find the recent _metadata as the checkpoint to recover (e.g as many proposals in FLINK-9043 suggest). However, there existed a "_meatadata" file does not mean the checkpoint have been completed as the writing to create the "_meatadata" file could break as some force quit (e.g. yarn application -kill).
> We could create the checkpoint meta stream to write data to file named as "_metadata.inprogress" and renamed it to "_metadata" once completed writing. By doing so, we could ensure the "_metadata" is not broken.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)