You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Yang Wang (JIRA)" <ji...@apache.org> on 2017/12/15 10:14:00 UTC
[jira] [Updated] (YARN-7660) NM node resource should be updated
through heartbeat when rmadmin updateNodeResource execute successfully
[ https://issues.apache.org/jira/browse/YARN-7660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yang Wang updated YARN-7660:
----------------------------
Summary: NM node resource should be updated through heartbeat when rmadmin updateNodeResource execute successfully (was: NodeManager metrics return wrong value after update node resource)
> NM node resource should be updated through heartbeat when rmadmin updateNodeResource execute successfully
> ---------------------------------------------------------------------------------------------------------
>
> Key: YARN-7660
> URL: https://issues.apache.org/jira/browse/YARN-7660
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Yang Wang
>
> {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