Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Fri, 11 Mar 2016 22:24:19 +0000 (UTC)
From: "Karthik Kambatla (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12941101.1456159609000.2448.1457735059395@Atlassian.JIRA>
In-Reply-To: <JIRA.12941101.1456159609000@Atlassian.JIRA>
References: <JIRA.12941101.1456159609000@Atlassian.JIRA>
 <JIRA.12941101.1456159609169@arcas>
Subject: [jira] [Commented] (YARN-4719) Add a helper library to maintain
 node state and allows common queries
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Karthik Kambatla commented on YARN-4719:
----------------------------------------

bq. Can we make ClusterNodeTracker an interface and make the current one in latest patch a Default Implementation ?
Good idea, but as Wangda says, we can do this lazily. The longer we wait, we probably also will have a good understanding of what the interface should be like. 

Updating patch to fix the nit shortly. 

> Add a helper library to maintain node state and allows common queries
> ---------------------------------------------------------------------
>
>                 Key: YARN-4719
>                 URL: https://issues.apache.org/jira/browse/YARN-4719
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: scheduler
>    Affects Versions: 2.8.0
>            Reporter: Karthik Kambatla
>            Assignee: Karthik Kambatla
>         Attachments: yarn-4719-1.patch, yarn-4719-2.patch, yarn-4719-3.patch, yarn-4719-4.patch, yarn-4719-5.patch
>
>
> The scheduler could use a helper library to maintain node state and allowing matching/sorting queries. Several reasons for this:
> # Today, a lot of the node state management is done separately in each scheduler. Having a single library will take us that much closer to reducing duplication among schedulers.
> # Adding a filtering/matching API would simplify node labels and locality significantly. 
> # An API that returns a sorted list for a custom comparator would help YARN-1011 where we want to sort by allocation and utilization for continuous/asynchronous and opportunistic scheduling respectively. 


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)