[jira] [Resolved] (FLINK-26985) With legacy restore mode, incremental checkpoints would be deleted by mistake

["Roman Khachatryan (Jira)" <ji...@apache.org>]

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

Roman Khachatryan resolved FLINK-26985.
---------------------------------------
    Resolution: Fixed

Merged into master as c0936deaf99390fc727acc8633e3be22e62f4bf5,
into release-1.15 as 5afff68c89c5e51a55f135109089c22d073b507f.

> With legacy restore mode, incremental 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, 1.16.0
>            Reporter: Yun Tang
>            Assignee: Roman Khachatryan
>            Priority: Blocker
>              Labels: pull-request-available
>             Fix For: 1.15.0, 1.16.0
>
>
> 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].
> Thanks for [~masteryhx] who found this problem in the manual test.



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