Karthik Kambatla commented on YARN-3304:

[~djp] - just to be clear, we are adding a deprecated method to a class we are 
marking Public first time in 2.7. I find it weird, but can live with it as long 
as we have a plan/timeline to remove it? 

[~hitesh] - is Tez okay with YARN removing these deprecated methods in 3.0.0? 
If yes, I would like for the javadoc for those methods to explicitly state that 
and a follow-up JIRA filed and fixed against trunk. If that is not okay, we are 
kidding ourselves by marking it deprecated. 

> 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