[
https://issues.apache.org/jira/browse/YARN-6862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16098609#comment-16098609
]
Jason Lowe commented on YARN-6862:
----------------------------------
I believe the case of it returning -1B is when the process exited just as the
resource monitor was going to examine it. It's an invalid result because there
is no process there. We should not be aggregating those results if that's
indeed the case.
> Nodemanager resource usage metrics sometimes are negative
> ---------------------------------------------------------
>
> Key: YARN-6862
> URL: https://issues.apache.org/jira/browse/YARN-6862
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
> Affects Versions: 2.8.2
> Reporter: YunFan Zhou
>
> When we collect real-time metrics of resource usage in NM, we found those
> values sometimes are invalid.
> For example, the following are values when collected at some point:
> "milliVcoresUsed":-5808,
> "currentPmemUsage":-1,
> "currentVmemUsage":-1,
> "cpuUsagePercentPerCore":-968.1026
> "cpuUsageTotalCoresPercentage":-24.202564,
> "pmemLimit":2147483648,
> "vmemLimit":4509715456
> There are many negative values, there may a bug in NM.
> We should fix it, because the real-time metrics of NM is pretty important for
> us sometimes.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
