[
https://issues.apache.org/jira/browse/FLINK-31765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17711487#comment-17711487
]
Matthias Pohl commented on FLINK-31765:
---------------------------------------
After a
[discussion|https://github.com/apache/flink/pull/22377/files#r1163828497] we
had in the PR, we concluded that no backport is necessary.
> Disable changelog backend for the StatefulJobSavepointMigrationITCase and
> StatefulJobWBroadcastStateMigrationITCase with RocksDB and checkpoints
> ------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-31765
> URL: https://issues.apache.org/jira/browse/FLINK-31765
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Coordination, Tests
> Affects Versions: 1.18.0
> Reporter: Matthias Pohl
> Assignee: Matthias Pohl
> Priority: Critical
> Labels: pull-request-available, test-stability
>
> In FLINK-31593 we discovered an instability when generating the migration
> test data for 1.17 for {{StatefulJobSavepointMigrationITCase}} and
> {{StatefulJobWBroadcastStateMigrationITCase}}. According to the discussion in
> FLINK-31593, we concluded that it's caused by a non-determinism that's
> happening in the changelog backend code. As a workaround, we're going to
> disable the changelog backend in these tests for now.
> We're not touching 1.16 because it didn't appear in that branch. The
> non-determinism seems to kick in only when generating the checkpoint files.
> For 1.17, we're gonna create a backport for consistency reasons because we
> have to enable it for the data generation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
