mukul-8 opened a new pull request, #27767:
URL: https://github.com/apache/flink/pull/27767
The test was flaky because it triggered a checkpoint immediately after
calling setAllExecutionsToRunning() without verifying that tasks actually
transitioned to RUNNING state. While state updates are synchronous, they
trigger async callbacks that need time to process. In slower CI environments,
the checkpoint coordinator may not have finished processing state updates,
causing the checkpoint trigger to be rejected and the test to timeout.
Added waitForAllTasksRunning() utility method to ensure all task executions
are in RUNNING state before triggering the checkpoint, eliminating the race
condition.
Verified with 300+ local test iterations without failure.
<!--
*Thank you very much for contributing to Apache Flink - we are happy that
you want to help us improve Flink. To help the community review your
contribution in the best possible way, please go through the checklist below,
which will get the contribution into a shape in which it can be best reviewed.*
*Please understand that we do not do this to make contributions to Flink a
hassle. In order to uphold a high standard of quality for code contributions,
while at the same time managing a large number of contributions, we need
contributors to prepare the contributions well, and give reviewers enough
contextual information for the review. Please also understand that
contributions that do not follow this guide will take longer to review and thus
typically be picked up with lower priority by the community.*
## Contribution Checklist
- Make sure that the pull request corresponds to a [JIRA
issue](https://issues.apache.org/jira/projects/FLINK/issues). Exceptions are
made for typos in JavaDoc or documentation files, which need no JIRA issue.
- Name the pull request in the form "[FLINK-XXXX] [component] Title of the
pull request", where *FLINK-XXXX* should be replaced by the actual issue
number. Skip *component* if you are unsure about which is the best component.
Typo fixes that have no associated JIRA issue should be named following
this pattern: `[hotfix] [docs] Fix typo in event time introduction` or
`[hotfix] [javadocs] Expand JavaDoc for PuncuatedWatermarkGenerator`.
- Fill out the template below to describe the changes contributed by the
pull request. That will give reviewers the context they need to do the review.
- Make sure that the change passes the automated tests, i.e., `mvn clean
verify` passes. You can set up Azure Pipelines CI to do that following [this
guide](https://cwiki.apache.org/confluence/display/FLINK/Azure+Pipelines#AzurePipelines-Tutorial:SettingupAzurePipelinesforaforkoftheFlinkrepository).
- Each pull request should address only one issue, not mix up code from
multiple issues.
- Each commit in the pull request has a meaningful commit message
(including the JIRA id)
- Once all items of the checklist are addressed, remove the above text and
this checklist, leaving only the filled out template below.
**(The sections below can be removed for hotfixes of typos)**
-->
## What is the purpose of the change
Fixes FLINK-38534 - flaky
LocalRecoveryTest.testStateSizeIsConsideredForLocalRecoveryOnRestart that
intermittently times out in CI.
Root Cause: The test triggers a checkpoint immediately after
setAllExecutionsToRunning() without verifying tasks have fully transitioned to
RUNNING state. While state updates are
synchronous, they trigger async callbacks (checkpoint coordinator, etc.)
that need time to process. In slower CI environments, the checkpoint
coordinator may not have finished processing,
causing the checkpoint trigger to be rejected and
waitForCheckpointInProgress() to timeout after 60 seconds.
Solution: Added waitForAllTasksRunning() utility method to ensure all task
executions are in RUNNING state before triggering the checkpoint.
This follows a similar approach to #27740 (FLINK-39182) which fixed
threading/timing issues in ExecutionGraphRestartTest.
## Brief change log
* Added waitForAllTasksRunning(ExecutionGraph) to SchedulerTestingUtils
* Updated LocalRecoveryTest to wait for all tasks to reach RUNNING state
before triggering checkpoint
## Verifying this change
Verified locally with 300+ test iterations without failure.
## Does this pull request potentially affect one of the following parts:
- Dependencies (does it add or upgrade a dependency): no
- The public API, i.e., is any changed class annotated with
`@Public(Evolving)`: no
- The serializers: no
- The runtime per-record code paths (performance sensitive): no
- Anything that affects deployment or recovery: JobManager (and its
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
- The S3 file system connector: no
## Documentation
- Does this pull request introduce a new feature? no
- If yes, how is the feature documented? (not applicable / docs / JavaDocs
/ not documented)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
