hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yang Wang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-7661) NodeManager metrics return wrong value after update node resource
Date Tue, 19 Dec 2017 05:25:00 GMT

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

Yang Wang commented on YARN-7661:
---------------------------------

[~jlowe], thanks for your review and commit.

> NodeManager metrics return wrong value after update node resource
> -----------------------------------------------------------------
>
>                 Key: YARN-7661
>                 URL: https://issues.apache.org/jira/browse/YARN-7661
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 2.7.0
>            Reporter: Yang Wang
>            Assignee: Yang Wang
>             Fix For: 3.1.0, 2.10.0, 2.9.1, 3.0.1, 2.8.4, 2.7.6
>
>         Attachments: YARN-7661.001.patch, YARN-7661.002.patch
>
>
> {code:title=NodeManagerMetrics.java}
>   public void addResource(Resource res) {
>     availableMB = availableMB + res.getMemorySize();
>     availableGB.incr((int)Math.floor(availableMB/1024d));
>     availableVCores.incr(res.getVirtualCores());
>   }
> {code}
> When the node resource was updated through RM-NM heartbeat, the NM metric will get wrong
value. 
> The root cause of this issue is that new resource has been added to availableMB, so not
needed to increase for availableGB again.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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


Mime
View raw message