[
https://issues.apache.org/jira/browse/YARN-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14387585#comment-14387585
]
Karthik Kambatla commented on YARN-3304:
----------------------------------------
[~vinodkv], [~hitesh] - given we have made this Public only in 2.7 which hasn't
been released yet, is it possible that we update Tez instead of YARN? It seems
like an overkill to add deprecated APIs for a previously non-Public API.
This should be the last time Tez fixes this. If we remove deprecated APIs in
the future, we will break Tez anyway. No?
> 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-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
(v6.3.4#6332)
