You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-dev@hadoop.apache.org by "liu bin (Jira)" <ji...@apache.org> on 2025/09/23 02:46:00 UTC
[jira] [Created] (YARN-11871) Make client retry when no active sub-cluster available
liu bin created YARN-11871:
------------------------------
Summary: 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
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: yarn-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org