You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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.
We're closing this stale PR because it has been open for 100 days with no activity. This isn't a judgement on the merit of the PR in any way. It's just a way of keeping the PR queue manageable.
If you feel like this was a mistake, or you would like to continue working on it, please feel free to re-open it and ask for a committer to remove the stale tag and review again.
Thanks all for your contribution.
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