[
https://issues.apache.org/jira/browse/YARN-11871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18050497#comment-18050497
]
ASF GitHub Bot commented on YARN-11871:
---------------------------------------
github-actions[bot] commented on PR #7997:
URL: https://github.com/apache/hadoop/pull/7997#issuecomment-3721375533
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.
> Make client retry when no active sub-cluster available
> ------------------------------------------------------
>
> Key: YARN-11871
> URL: https://issues.apache.org/jira/browse/YARN-11871
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: federation
> Reporter: liu bin
> Priority: Major
> Labels: pull-request-available
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
