-
Notifications
You must be signed in to change notification settings - Fork 9.1k
YARN-11871. Make client retry when no active sub-cluster available. #7997
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
Open
liubin101
wants to merge
4
commits into
apache:trunk
Choose a base branch
from
liubin101:YARN-11871
base: trunk
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+166
−96
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
💔 -1 overall
This message was automatically generated. |
💔 -1 overall
This message was automatically generated. |
💔 -1 overall
This message was automatically generated. |
💔 -1 overall
This message was automatically generated. |
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.
Description of PR
Under the YARN Federation architecture, when there's only one sub-cluster, or when multiple sub-clusters exist but a queue is configured to submit exclusively to a specific sub-cluster, the following problem occurs: If this target sub-cluster failover, its state will remain "non-active" until the new active RM completes registration and sends the first heartbeat (default 30 seconds later). During this window, any client attempting to submit applications will fail with the error: "No active SubCluster available to submit the request" or "No positive weight found on active subclusters".
In non-YARN Federation setups, clients automatically retry during RM failover. We expect this retry behavior to be preserved when transitioning to the YARN Federation architecture.
How was this patch tested?
unit test