[
https://issues.apache.org/jira/browse/YARN-4718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15157233#comment-15157233
]
Karthik Kambatla commented on YARN-4718:
----------------------------------------
I was thinking of the following variable renames (and the corresponding
methods) that would simplify the names as well:
# usedResource -> allocated or allocatedResource
# availableResource -> unallocated or unallocatedResource
# totalResourceCapability -> capacity or leave it as is
# While at it, I am open to cleaning the class up a little - e.g.
{{launchedContainers}} definition uses Java6 way of specifying generics.
> 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
>
> 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)
