-
Notifications
You must be signed in to change notification settings - Fork 4.5k
Fix Flink IllegalThreadStateException on Java 8 #36730
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
Merged
Abacn
merged 4 commits into
apache:master
from
aIbrahiim:32949-PostCommit-Java-ValidatesRunner-Flink-Java8
Nov 6, 2025
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
3b9091d
Fix Flink IllegalThreadStateException on Java 8
aIbrahiim 57c07f6
Fixed both Spotless formatting issues
aIbrahiim 1860c25
Applied Flink ThreadGroup fix to Java 8 batch jobs in local environme…
aIbrahiim 77c0bc6
Added executionEnv param
aIbrahiim File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
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.
Busy wait is generally not desired but for band-aid fix I think it's fine. We should narrow the scenario that introduced 2 seconds latency
this only affects in-memory flink clusters, and also only affects batch jobs (':runners:flink:1.19:validatesRunnerBatch'.). Can we call wait only for batch?
Can we check whether FlinkPipelineOptions.getFlinkMaster is a "org.apache.flink.api.java.ExecutionEnvironment.LocalEnvironment" and only do the busy wait for local environment?
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.
Okay I agree we can narrow the scope to wait for batch jobs and detect the environment and apply it for local env.
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.
sorry realize this parameter is actually useful. We can do
this is more reliable than check getFlinkMaster below
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.
Added the parameter