You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Yun Tang (Jira)" <ji...@apache.org> on 2022/04/01 10:22:00 UTC
[jira] [Commented] (FLINK-26985) With legacy restore mode, incremantal checkpoints would be deleted by mistake
[ https://issues.apache.org/jira/browse/FLINK-26985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17515852#comment-17515852 ]
Yun Tang commented on FLINK-26985:
----------------------------------
I think this error is caused by the refactoring introduced in FLINK-24611, [~roman] would you please take a look?
> With legacy restore mode, incremantal checkpoints would be deleted by mistake
> -----------------------------------------------------------------------------
>
> Key: FLINK-26985
> URL: https://issues.apache.org/jira/browse/FLINK-26985
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Checkpointing
> Affects Versions: 1.15.0
> Reporter: Yun Tang
> Priority: Blocker
>
> Before flink-1.15, the restored checkpoint would be regsiterd and not discard on subsume, which means the restored incremental checkpoint would have one more reference counting to avoid discard.
> However, after state registry refactored, we could delete artificats in the restored incremental checkpoint with legacy restore mode.
> The error could be reproduced via {{ResumeCheckpointManuallyITCase#testExternalizedIncrementalRocksDBCheckpointsStandalone}} in my [local branch|https://github.com/Myasuka/flink/tree/legacy-error].
--
This message was sent by Atlassian Jira
(v8.20.1#820001)