Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Tue, 18 Mar 2014 08:31:44 +0000 (UTC)
From: "Karthik Kambatla (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12682817.1386208393699.95386.1395131504450@arcas>
In-Reply-To: <JIRA.12682817.1386208393699@arcas>
References: <JIRA.12682817.1386208393699@arcas>
Subject: [jira] [Commented] (YARN-1474) Make schedulers services
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Karthik Kambatla commented on YARN-1474:
----------------------------------------

Skimmed through the patch. Looks reasonable. Can we fix the findbugs warnings as well.

The patch looks benign, but given the patch touches all schedulers, I wonder if we should commit this only to branch-2 and not branch-2.4 just yet. 

> Make schedulers services
> ------------------------
>
>                 Key: YARN-1474
>                 URL: https://issues.apache.org/jira/browse/YARN-1474
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: scheduler
>    Affects Versions: 2.3.0
>            Reporter: Sandy Ryza
>            Assignee: Tsuyoshi OZAWA
>         Attachments: YARN-1474.1.patch, YARN-1474.2.patch, YARN-1474.3.patch, YARN-1474.4.patch, YARN-1474.5.patch, YARN-1474.6.patch, YARN-1474.7.patch
>
>
> Schedulers currently have a reinitialize but no start and stop.  Fitting them into the YARN service model would make things more coherent.


--
This message was sent by Atlassian JIRA
(v6.2#6252)