Details
-
Improvement
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
1.10.0
Description
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.
Attachments
Issue Links
- is related to
-
FLINK-9043 Introduce a friendly way to resume the job from externalized checkpoints automatically
- Reopened
-
FLINK-9325 generate the _meta file for checkpoint only when the writing is truly successful
- Closed
-
FLINK-22008 writing metadata is not an atomic operation, we should add a commit logic
- Closed
- supercedes
-
FLINK-22008 writing metadata is not an atomic operation, we should add a commit logic
- Closed
- links to