[FLINK-9106] [rpc] Add UnfencedMainThreadExecutor to FencedRpcEndpoint #5784
Conversation
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
The UnfencedMainThreadExecutor executed Runnables in the main thread context without checking the fencing token. This is important to set a new fencing token, for example.
tillrohrmann
added a commit
to tillrohrmann/flink
that referenced
this pull request
Mar 29, 2018
The UnfencedMainThreadExecutor executed Runnables in the main thread context without checking the fencing token. This is important to set a new fencing token, for example. This closes apache#5784.
asfgit
pushed a commit
that referenced
this pull request
Mar 29, 2018
The UnfencedMainThreadExecutor executed Runnables in the main thread context without checking the fencing token. This is important to set a new fencing token, for example. This closes #5784.
sampathBhat
pushed a commit
to sampathBhat/flink
that referenced
this pull request
Jul 26, 2018
The UnfencedMainThreadExecutor executed Runnables in the main thread context without checking the fencing token. This is important to set a new fencing token, for example. This closes apache#5784.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 UnfencedMainThreadExecutor executed Runnables in the main thread context without
checking the fencing token. This is important to set a new fencing token, for example.
Verifying this change
AsyncCallsTest#testUnfencedMainThreadExecutorDoes this pull request potentially affect one of the following parts:
@Public(Evolving): (no)Documentation