[
https://issues.apache.org/jira/browse/YARN-7659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Lowe resolved YARN-7659.
------------------------------
Resolution: Duplicate
> NodeManager metrics return wrong value after update resource
> ------------------------------------------------------------
>
> Key: YARN-7659
> URL: https://issues.apache.org/jira/browse/YARN-7659
> 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-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org
