[
https://issues.apache.org/jira/browse/FLINK-40476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18124727#comment-18124727
]
Ravikiran kalal commented on FLINK-40476:
-----------------------------------------
Hi, I'd like to work on this. I confirmed the behaviour in the code: the
Changelog state backend does not override
StateBackend#supportsNoClaimRestoreMode(), so after a NO_CLAIM restore the
forced full checkpoint fails in StreamTask#checkForcedFullSnapshotSupport. I
have a docs change ready that states the CLAIM requirement in the "Enabling
Changelog" steps (English and Chinese pages), adds a warning describing the
failure, and fixes the stale config anchor in the limitations list. Could a
committer please assign this ticket to me?
> Clarify that the Changelog state backend requires CLAIM restore mode
> (NO_CLAIM unsupported)
> -------------------------------------------------------------------------------------------
>
> Key: FLINK-40476
> URL: https://issues.apache.org/jira/browse/FLINK-40476
> Project: Flink
> Issue Type: Improvement
> Components: Documentation
> Reporter: Santwana Verma
> Priority: Minor
> Labels: pull-request-available
>
> The Changelog state backend docs state "Resuming from both savepoints and
> checkpoints is supported" but don't make clear that NO_CLAIM restore mode
> (the default) is unsupported. A changelog-enabled job resumed in `NO_CLAIM`
> restores successfully but fails on its first checkpoint with
> `IllegalStateException: ... does not support enforcing a full snapshot`. The
> existing "NO_CLAIM mode not supported" limitation bullet is easy to miss and
> contradicts the "resuming supported" statement. Related ticket:
> https://issues.apache.org/jira/browse/FLINK-38307
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
