[
https://issues.apache.org/jira/browse/FLINK-25872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17524886#comment-17524886
]
Roman Khachatryan commented on FLINK-25872:
-------------------------------------------
I think your understanding is correct [~dwysakowicz] .
> Question: Is the problem related to state handles registered in
> {{{}SharedStateRegistry{}}}? Or does it affect non-shared, private parts of
> the initial checkpoint? If I understand correctly, it does affect also
> originally private parts of the initial checkpoint, right?
Right, (it does affect also originally private parts of the initial checkpoint)
The motivation behind this ticket is to lower the downtime (caused by
taking/restoring from a savepoint). Some setups might simply not use savepoints
for that reason.
Support for switching in the opposite direction (changelog on -> off) will be
added in FLINK-23252.
> Restoring from non-changelog checkpoint with changelog state-backend enabled
> in CLAIM mode discards state in use
> ----------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-25872
> URL: https://issues.apache.org/jira/browse/FLINK-25872
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Checkpointing, Runtime / State Backends
> Reporter: Yun Tang
> Assignee: Yanfei Lei
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.16.0
>
>
> If we restore from checkpoint with changelog state-backend enabled in
> snapshot CLAIM mode, the restored checkpoint would be discarded on subsume.
> This invalidates newer/active checkpoints because their materialized part is
> discarded (for incremental wrapped checkpoints, their private state is
> discarded). This bug is like FLINK-25478.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
