Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Fri, 6 Dec 2013 02:22:35 +0000 (UTC)
From: "Vinod Kumar Vavilapalli (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12666765.1378244747542.82329.1386296555780@arcas>
In-Reply-To: <JIRA.12666765.1378244747542@arcas>
References: <JIRA.12666765.1378244747542@arcas>
Subject: [jira] [Commented] (YARN-1139) [Umbrella] Convert all RM components
 to Services
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Vinod Kumar Vavilapalli commented on YARN-1139:
-----------------------------------------------

Is it absolutely necessary to convert all of the components to be services. Can we focus on the absolute minimum needed? And what would that minimal set be?

> [Umbrella] Convert all RM components to Services
> ------------------------------------------------
>
>                 Key: YARN-1139
>                 URL: https://issues.apache.org/jira/browse/YARN-1139
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: resourcemanager
>    Affects Versions: 2.1.0-beta
>            Reporter: Karthik Kambatla
>            Assignee: Tsuyoshi OZAWA
>
> Some of the RM components - state store, scheduler etc. are not services. Converting them to services goes well with the "Always On" and "Active" service separation proposed on YARN-1098.
> Given that some of them already have start(), stop() methods, it should not be too hard to convert them to services.
> That would also be a cleaner way of addressing YARN-1125.


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