[FLINK-40456][datastream] AsyncWaitOperator can permanently drop an element's result when timeout races with a retry - #29005
Open
snuyanzin wants to merge 1 commit into
Open
[FLINK-40456][datastream] AsyncWaitOperator can permanently drop an element's result when timeout races with a retry#29005snuyanzin wants to merge 1 commit into
AsyncWaitOperator can permanently drop an element's result when timeout races with a retry#29005snuyanzin wants to merge 1 commit into
Conversation
… element's result when timeout races with a retry
Collaborator
Contributor
Author
|
@lincoln-lil I noticed you made some related changes here as well |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is the purpose of the change
The PR to fix
AsyncWaitOperatorrace between retry and timeoutAlso it is a step towards jdk25
Brief change log
AsyncWaitOperator
Verifying this change
test is added
Does this pull request potentially affect one of the following parts:
@Public(Evolving): (no)Documentation
Was generative AI tooling used to co-author this PR?
Generated-by: [Tool Name and Version]