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.
Add drain support for Dataflow and Flink #38786
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Add drain support for Dataflow and Flink #38786
Changes from all commits
33d84f6242d9e7a6bc89cFile filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If the
drainSavepointFuturecompletes exceptionally (e.g., if the stop-with-savepoint operation fails), callinggetState()will currently throw aRuntimeExceptionand crash the caller. Instead, we should be more robust: if the drain operation failed, the job is likely still running or in its previous state. We can checkisCompletedExceptionally()and, if true, fall back to querying the actual Flink job status viajobClient.getJobStatus().There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can improve the robustness of the
drain()method in several ways:drainFuture.isCompletedExceptionally()), we should allow the user to retry the drain operation rather than permanently returning the cached failure.drain()is declared to throwIOException, we should wrap and throwIOExceptioninstead ofRuntimeExceptionwhen the future fails.getDrainStatelogic directly intodrain()and remove the helper method entirely, making the code cleaner.Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.