[
https://issues.apache.org/jira/browse/FLINK-39140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18130981#comment-18130981
]
Martijn Visser edited comment on FLINK-39140 at 10/23/26, 2:23 PM:
-------------------------------------------------------------------
Backported to release-1.20:
[FLINK-39140][test] Fix MAX_RETAINED_CHECKPOINTS not effective in
UnalignedCheckpointRescaleWithMixedExchangesITCase
1263b16bc6d536ba0fd0a92646c24d9ce9f74357
was (Author: martijnvisser):
Also backported to release-1.20: 1263b16bc6d536ba0fd0a92646c24d9ce9f74357
> [FLINK-39140][checkpoint] Allow multiple rescales in Unaligned Checkpoint
> ITCases to perform checkpointing during recovery
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-39140
> URL: https://issues.apache.org/jira/browse/FLINK-39140
> Project: Flink
> Issue Type: Sub-task
> Reporter: Rui Fan
> Assignee: Rui Fan
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.3.0, 1.20.6
>
>
> Current Unaligned Checkpoint ITCases only restart once from a normal
> checkpoint. They do not cover restoring from a checkpoint produced by
> recovery phase — which is the key scenario for checkpointing during recovery.
> *Proposed mechanism:* After restoring from a checkpoint, wait for the first
> new checkpoint to be produced, then immediately trigger a restart from it.
> Repeat for a configurable number of rounds (≥ 2). Whether to rescale depends
> on the specific test case.
> This mechanism works on the current master (validating normal checkpoint
> recovery). Once checkpointing during recovery is enabled, the same tests
> automatically cover recovery-phase checkpoint scenarios.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
