Skip to content

Conversation

noorall
Copy link
Contributor

@noorall noorall commented Sep 28, 2025

What is the purpose of the change

Fix unstable BatchJobRecoveryTest

Brief change log

Avoid test failures due to task restarts after failover.

Does this pull request potentially affect one of the following parts:

  • Dependencies (does it add or upgrade a dependency): (yes / no)
  • The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
  • The serializers: (yes / no / don't know)
  • The runtime per-record code paths (performance sensitive): (yes / no / don't know)
  • Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (yes / no / don't know)
  • The S3 file system connector: (yes / no / don't know)

Documentation

  • Does this pull request introduce a new feature? (yes / no)
  • If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

@flinkbot
Copy link
Collaborator

flinkbot commented Sep 28, 2025

CI report:

Bot commands The @flinkbot bot supports the following commands:
  • @flinkbot run azure re-run the last Azure build

@noorall noorall force-pushed the fix-adaptive-batch-recovery branch 3 times, most recently from d6abb4e to 90dd583 Compare September 30, 2025 09:17
@noorall
Copy link
Contributor Author

noorall commented Sep 30, 2025

@zhuzhurk Thanks for your review. I've pushed a fixup commit to address your comments.

Copy link
Contributor

@zhuzhurk zhuzhurk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

@noorall noorall force-pushed the fix-adaptive-batch-recovery branch from 1437e02 to b943355 Compare September 30, 2025 09:44
@noorall
Copy link
Contributor Author

noorall commented Oct 2, 2025

@flinkbot run azure

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants