Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Tue, 7 May 2013 16:19:16 +0000 (UTC)
From: "Timothy St. Clair (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12626535.1357647224993.281577.1367943556496@arcas>
In-Reply-To: <JIRA.12626535.1357647224993@arcas>
References: <JIRA.12626535.1357647224993@arcas>
Subject: [jira] [Commented] (YARN-322) Add cpu information to queue metrics
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Timothy St. Clair commented on YARN-322:
----------------------------------------

I'm still on my learning curve, but from what I have seen there is limited information that is passed by the Resource.  Given some of the other JIRA's around memory, wouldn't it make sense to expand the scope to enable some type of NVP set for Node attributes, with cpu capabilities being part of that set.  

One could envision the scope expanding to include GPUs, interconnect capabilities, etc, as not all machines are =.  

This discrimination will allow ApplicationManagers to better filter desired resources for their problem. 

Also feel free to tell me I'm wrong, as I'm still learning ;-). 


> Add cpu information to queue metrics
> ------------------------------------
>
>                 Key: YARN-322
>                 URL: https://issues.apache.org/jira/browse/YARN-322
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: capacityscheduler, scheduler
>            Reporter: Arun C Murthy
>            Assignee: Arun C Murthy
>             Fix For: 2.0.5-beta
>
>
> Post YARN-2 we need to add cpu information to queue metrics.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira