Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Sat, 7 Dec 2013 01:23:36 +0000 (UTC)
From: "Karthik Kambatla (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12661617.1375650313919.90569.1386379416358@arcas>
In-Reply-To: <JIRA.12661617.1375650313919@arcas>
References: <JIRA.12661617.1375650313919@arcas>
Subject: [jira] [Updated] (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:all-tabpanel ]

Karthik Kambatla updated YARN-1028:
-----------------------------------

    Attachment: yarn-1028-4.patch

My bad - was setting rm-ids even for non-HA cases. Fixed that.

By the way, none of the minicluster configs are in yarn-default.xml; didn't include the new one created here either.

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