You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-dev@hadoop.apache.org by "Karthik Kambatla (JIRA)" <ji...@apache.org> on 2016/02/28 19:17:18 UTC

[jira] [Resolved] (YARN-4718) Rename variables in SchedulerNode to reduce ambiguity post YARN-1011

     [ https://issues.apache.org/jira/browse/YARN-4718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karthik Kambatla resolved YARN-4718.
------------------------------------
       Resolution: Fixed
     Hadoop Flags: Reviewed
    Fix Version/s: 2.9.0

Thanks for picking this up, [~elgoiri]. Just committed to trunk and branch-2. 

> Rename variables in SchedulerNode to reduce ambiguity post YARN-1011
> --------------------------------------------------------------------
>
>                 Key: YARN-4718
>                 URL: https://issues.apache.org/jira/browse/YARN-4718
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: scheduler
>    Affects Versions: 2.8.0
>            Reporter: Karthik Kambatla
>            Assignee: Inigo Goiri
>             Fix For: 2.9.0
>
>         Attachments: YARN-4718-v000.patch, YARN-4718-v001.patch, YARN-4718-v002.patch, YARN-4718-v003.patch, YARN-4718-v004.patch
>
>
> As discussed in YARN-1011, we are planning to add a few more variables regarding utilization to SchedulerNode. To ensure the new variables are descriptive and don't lead to confusion, the existing variables could use some renaming. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)