You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Matthias Pohl (Jira)" <ji...@apache.org> on 2024/03/25 16:11:00 UTC
[jira] [Commented] (FLINK-21400) Attempt numbers are not maintained across restarts
[ https://issues.apache.org/jira/browse/FLINK-21400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17830556#comment-17830556 ]
Matthias Pohl commented on FLINK-21400:
---------------------------------------
Enabling the tests for AdaptiveScheduler (see FLINK-34409):
* master
** [a1d17ccf0eec7dd614146e22832037cadd7abe5c|https://github.com/apache/flink/commit/a1d17ccf0eec7dd614146e22832037cadd7abe5c]
* 1.19
** [4fc36e9abaa8cc2d0e01c1e389b449f563b87e8e|https://github.com/apache/flink/commit/4fc36e9abaa8cc2d0e01c1e389b449f563b87e8e]
* 1.18
** [8f6890fbd757f3d3c9c891ea9139a1e5ac3412a2|https://github.com/apache/flink/commit/8f6890fbd757f3d3c9c891ea9139a1e5ac3412a2]
> Attempt numbers are not maintained across restarts
> --------------------------------------------------
>
> Key: FLINK-21400
> URL: https://issues.apache.org/jira/browse/FLINK-21400
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Coordination
> Reporter: Chesnay Schepler
> Assignee: Chesnay Schepler
> Priority: Critical
> Labels: pull-request-available
> Fix For: 1.13.0
>
>
> The DeclarativeScheduler discards the ExecutionGraph on each restart attempt, as a result of which the attempt number remains 0.
> Various tests use the attempt number to determine whether an exception should be thrown, and thus continue to throw exceptions on each restart.
> Affected tests:
> UnalignedCheckpointTestBase
> UnalignedCheckpointITCase
> ProcessingTimeWindowCheckpointingITCase
> LocalRecoveryITCase
> EventTimeWindowCheckpointingITCase
> EventTimeAllWindowCheckpointingITCase
> FileSinkITBase#testFileSink
--
This message was sent by Atlassian Jira
(v8.20.10#820010)