Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 3 Nov 2016 15:41:58 +0000 (UTC)
From: "Inigo Goiri (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12988375.1468259619000.174730.1478187718608@Atlassian.JIRA>
In-Reply-To: <JIRA.12988375.1468259619000@Atlassian.JIRA>
References: <JIRA.12988375.1468259619000@Atlassian.JIRA> <JIRA.12988375.1468259619362@arcas>
Subject: [jira] [Updated] (YARN-5356) NodeManager should communicate
 physical resource capability to ResourceManager
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 03 Nov 2016 15:42:00 -0000


     [ https://issues.apache.org/jira/browse/YARN-5356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Inigo Goiri updated YARN-5356:
------------------------------
    Attachment: YARN-5356.008.patch

Setting ResourceCalculatorPlugin consistently for the NM and removing read/write lock.

> NodeManager should communicate physical resource capability to ResourceManager
> ------------------------------------------------------------------------------
>
>                 Key: YARN-5356
>                 URL: https://issues.apache.org/jira/browse/YARN-5356
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: nodemanager, resourcemanager
>    Affects Versions: 3.0.0-alpha1
>            Reporter: Nathan Roberts
>            Assignee: Inigo Goiri
>              Labels: oct16-medium
>         Attachments: YARN-5356.000.patch, YARN-5356.001.patch, YARN-5356.002.patch, YARN-5356.002.patch, YARN-5356.003.patch, YARN-5356.004.patch, YARN-5356.005.patch, YARN-5356.006.patch, YARN-5356.007.patch, YARN-5356.008.patch
>
>
> Currently ResourceUtilization contains absolute quantities of resource used (e.g. 4096MB memory used). It would be good if the NM also communicated the actual physical resource capabilities of the node so that the RM can use this data to schedule more effectively (overcommit, etc)
> Currently the only available information is the Resource the node registered with (or later updated using updateNodeResource). However, these aren't really sufficient to get a good view of how utilized a resource is. For example, if a node reports 400% CPU utilization, does that mean it's completely full, or barely utilized? Today there is no reliable way to figure this out.
> [~elgoiri] - Lots of good work is happening in YARN-2965 so curious if you have thoughts/opinions on this?


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

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org