Karthik Kambatla commented on YARN-3304:

[~hitesh] - thanks for okay their removal in 3.0.0. The reason I was asking - 
our compat policy requires us to deprecate an API for an entire major release 
before being removed in the next one. This is an ambiguous case, because this 
API is essentially born deprecated :)

[~djp] - can you add a blurb in the javadoc to say we are going to remove this 
in 3.0.0. Also, can we deprecate and add the blurb to 
{{getCumulativeRssmem(int)}} and {{getCumulativeVmem(int)}}? 

> 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: Junping Du
>            Priority: Blocker
>             Fix For: 2.7.0
>         Attachments: YARN-3304-appendix-v2.patch, YARN-3304-appendix.patch, 
> YARN-3304-v2.patch, YARN-3304-v3.patch, YARN-3304-v4-boolean-way.patch, 
> YARN-3304-v4-negative-way-MR.patch, YARN-3304-v4-negtive-value-way.patch, 
> YARN-3304-v6-no-rename.patch, YARN-3304-v6-with-rename.patch, 
> YARN-3304-v7.patch, YARN-3304-v8.patch, YARN-3304.patch, yarn-3304-5.patch
> 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

Reply via email to