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

Anubhav Dhoot commented on YARN-3304:
-------------------------------------

The intention of setting -1 as was for this issue (distinguishing unavailable 
vs actually zero). 
Ideally we should prevent adding the metrics to collection until they are 
available. One possibility is doing it at ContainerMetrics#recordCpuUsage.
Suggest investigating if this ideal case is achievable, and if not i am fine 
with making these 0 to be consistent.

> 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)

Reply via email to