Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Fri, 13 Dec 2013 22:56:09 +0000 (UTC)
From: "Karthik Kambatla (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12661617.1375650313919.35284.1386975369475@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=13848027#comment-13848027 ] 

Karthik Kambatla commented on YARN-1028:
----------------------------------------

bq. RMFailoverProxyProvider doesn't need to be public? For java users, the clients are the public interfaces, so they don't need to use these directly?
What if someone wants to implement their own RMFailoverProxyProvider? They need to know if they can rely on the interface? 

> 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-2.patch, yarn-1028-3.patch, yarn-1028-4.patch, yarn-1028-5.patch, yarn-1028-6.patch, yarn-1028-7.patch, yarn-1028-8.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.4#6159)