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

Posted to issues@flink.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2026/07/29 11:06:00 UTC

[jira] [Updated] (FLINK-40254) Document checkpoint behavior after a CLAIM-mode restore from a NATIVE savepoint

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

ASF GitHub Bot updated FLINK-40254:
-----------------------------------
    Labels: pull-request-available  (was: )

> Document checkpoint behavior after a CLAIM-mode restore from a NATIVE savepoint
> -------------------------------------------------------------------------------
>
>                 Key: FLINK-40254
>                 URL: https://issues.apache.org/jira/browse/FLINK-40254
>             Project: Flink
>          Issue Type: Improvement
>            Reporter: Aleksandr Savonin
>            Assignee: Aleksandr Savonin
>            Priority: Minor
>              Labels: pull-request-available
>
> After https://issues.apache.org/jira/browse/FLINK-39964, the first incremental checkpoint(s) taken after a CLAIM-mode restore from a NATIVE savepoint reference the reused savepoint files by their absolute location. The "Resuming from savepoints" page [https://nightlies.apache.org/flink/flink-docs-stable/docs/ops/state/savepoints/#resuming-from-savepoints] should clarify: the savepoint directory remains referenced (and, in CLAIM mode, managed/deleted by Flink) until those checkpoints are subsumed, such checkpoints are not relocatable - consistent with incremental checkpoints generally.



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