hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun Suresh (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4496) Improve HA ResourceManager Failover detection on the client
Date Thu, 21 Jan 2016 00:05:39 GMT

    [ https://issues.apache.org/jira/browse/YARN-4496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15109780#comment-15109780

Arun Suresh commented on YARN-4496:

bq. This method actually uses this flag
Correct.. but what I meant to say was, why you would want to add an extra boolean attribute
to the {{createRetryPolicy}} function, when it is possible to evaluate it using {{HAUtil.isHAEnabled(conf)}}
(like it was done before).

bq. Do you mean the startRMInThread in the test case? that thread just call a single method..
Got it... I thought you had actually started an RM in a thread (maybe, just rename it to makeRMActive)

> 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: Jian He
>         Attachments: YARN-4496.1.patch, YARN-4496.2.patch, YARN-4496.3.patch, YARN-4496.4.patch
> 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

This message was sent by Atlassian JIRA

View raw message