[
https://issues.apache.org/jira/browse/YARN-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14372965#comment-14372965
]
Vinod Kumar Vavilapalli commented on YARN-3304:
-----------------------------------------------
Coming back to this again.
I think the problem of unavailable metrics existing for other APIs too.
Let's make this 0 and consistent, and track the unavailability issues
separately?
[~djp] / [[email protected]] / [~adhoot], can we get going? It's blocking
2.7, appreciate your response. Tx.
> ResourceCalculatorProcessTree#getCpuUsagePercent default return value is
> inconsistent with other getters
> --------------------------------------------------------------------------------------------------------
>
> Key: YARN-3304
> URL: https://issues.apache.org/jira/browse/YARN-3304
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
> Reporter: Junping Du
> Assignee: Karthik Kambatla
> Priority: Blocker
>
> Per discussions in YARN-3296, getCpuUsagePercent() will return -1 for
> unavailable case while other resource metrics are return 0 in the same case
> which sounds inconsistent.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
