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

Allen Wittenauer commented on YARN-3304:
----------------------------------------

bq. To change tez, we will need to create shims based on which version of 
hadoop, the plugin is being built for. 

The Tez community could have opted to work the Hadoop community to make this 
public.  They didn't.  That's the risks when a program hits a private 
interface.  Tez wouldn't be the first to make such a stupid mistake and won't 
be the first to have to pay the consequences. 

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

Reply via email to