Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Mon, 28 Oct 2013 17:11:12 +0000 (UTC)
From: "Karthik Kambatla (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12593946.1339916854719.11847.1382980272331@arcas>
In-Reply-To: <JIRA.12593946.1339916854719@arcas>
References: <JIRA.12593946.1339916854719@arcas>
Subject: [jira] [Commented] (YARN-149) ResourceManager (RM)
 High-Availability (HA)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Karthik Kambatla commented on YARN-149:
---------------------------------------

YARN-1281. Haven't had a chance to look into it yet. 

> ResourceManager (RM) High-Availability (HA)
> -------------------------------------------
>
>                 Key: YARN-149
>                 URL: https://issues.apache.org/jira/browse/YARN-149
>             Project: Hadoop YARN
>          Issue Type: New Feature
>            Reporter: Harsh J
>            Assignee: Bikas Saha
>         Attachments: rm-ha-phase1-approach-draft1.pdf, rm-ha-phase1-draft2.pdf, YARN ResourceManager Automatic Failover-rev-07-21-13.pdf, YARN ResourceManager Automatic Failover-rev-08-04-13.pdf
>
>
> This jira tracks work needed to be done to support one RM instance failing over to another RM instance so that we can have RM HA. Work includes leader election, transfer of control to leader and client re-direction to new leader.


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