[FLINK-7504] Fence the ResourceManager #4582
Closed
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
Properly fences the ResourceManager by letting it extend the FencedRpcEndpoint.
Moreover, this PR introduces a ResourceManagerId which replaces the UUID as
leader id/fencing token. This will give us more type safety when defining rpc
interfaces.
This PR is based on #4580 and #4578.
Brief change log
ResourceManagerextend fromFencedRpcEndpointResourceManagerIdwhich replaces theResourceManager'sleader idResourceManagerGatewayto not require explicitly sending theResourceManagerId(this is implicitly done by theFencedAkkaInvocationHandler)RetryingRegistrationto connect toFencedRpcEndpointsVerifying this change
This change is already covered by existing tests, such as the
FencedRpcEndpointTest.Does this pull request potentially affect one of the following parts:
@Public(Evolving): (no)Documentation