Vinod Kumar Vavilapalli commented on YARN-3304:

Interesting discussion.

The expectation on deprecated APIs is that they are going to be deleted in the 
next major release. We do not need to explicitly say so for each deprecated API.

That said, in practice, we don't tend to remove deprecated APIs in the next 
release itself. For example, we have tried this with old MR job APIs which we 
went back on given the very long tail. So even though we set the expectation of 
deprecated-APIs removal in next release, we conservatively do so a little later 
in practice.

Back to the patch. [~djp], can you address these?
bq. Also, can we deprecate (..) getCumulativeRssmem(int) and 

> 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