Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Fri, 15 Nov 2013 01:57:21 +0000 (UTC)
From: "Bikas Saha (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12661617.1375650313919.78263.1384480641570@arcas>
In-Reply-To: <JIRA.12661617.1375650313919@arcas>
References: <JIRA.12661617.1375650313919@arcas>
Subject: [jira] [Commented] (YARN-1028) Add FailoverProxyProvider like
 capability to RMProxy
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Bikas Saha commented on YARN-1028:
----------------------------------

How do we know that the standby RM will be ready in that much time (if the current RM has crashed)? What kind of network errors cause failoverOnNetworkException to be triggered? Can they be caused due to glitches in the network, thus we would fail over to the standby and failback again?

> Add FailoverProxyProvider like capability to RMProxy
> ----------------------------------------------------
>
>                 Key: YARN-1028
>                 URL: https://issues.apache.org/jira/browse/YARN-1028
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Bikas Saha
>            Assignee: Karthik Kambatla
>         Attachments: yarn-1028-1.patch, yarn-1028-draft-cumulative.patch
>
>
> RMProxy layer currently abstracts RM discovery and implements it by looking up service information from configuration. Motivated by HDFS and using existing classes from Common, we can add failover proxy providers that may provide RM discovery in extensible ways.


--
This message was sent by Atlassian JIRA
(v6.1#6144)