hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jian He (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4496) Improve HA ResourceManager Failover detection on the client
Date Wed, 20 Jan 2016 19:26:39 GMT

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

Jian He commented on YARN-4496:
-------------------------------

yeah, I actually tried to make them common when I started writing the patch initially. but
because of some other logic divergence,  making them common requires nontrival refactoring
on RM and maybe hdfs too. I'd like to keep them as is and open a jira separately 

> 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
>
>
> 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)

Mime
View raw message