Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Wed, 23 Dec 2015 02:21:46 +0000 (UTC)
From: "Arun Suresh (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12923901.1450837272000.98686.1450837306765@Atlassian.JIRA>
In-Reply-To: <JIRA.12923901.1450837272000@Atlassian.JIRA>
References: <JIRA.12923901.1450837272000@Atlassian.JIRA>
 <JIRA.12923901.1450837272933@arcas>
Subject: [jira] [Created] (YARN-4496) Improve HA ResourceManager Failover
 detection on the client
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Arun Suresh created YARN-4496:
---------------------------------

             Summary: Improve HA ResourceManager Failover detection on the client
                 Key: YARN-4496
                 URL: https://issues.apache.org/jira/browse/YARN-4496
             Project: Hadoop YARN
          Issue Type: Improvement
          Components: client, resourcemanager
            Reporter: Arun Suresh
            Assignee: Arun Suresh


HDFS deployments can currently use the {{RequestHedgingProxyProvider}} to improve Namenode failover detection in the client. It does this by concurrently trying all namenodes and picks the namenode that returns the fastest with a successful response as the active node.

It would be useful to have a similar ProxyProvider for the Yarn RM (it can possibly be done by converging some the class hierarchies to use the same ProxyProvider)

This would especially be useful for large YARN deployments with multiple standby RMs where clients will be able to pick the active RM without having to traverse a list of configured RMs. 


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)