[
https://issues.apache.org/jira/browse/YARN-2696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14496881#comment-14496881
]
Jian He commented on YARN-2696:
-------------------------------
few minor comments
- add a comment why no_label max resource is treated separately.
{code}
if (nodePartition == null
|| nodePartition.equals(RMNodeLabelsManager.NO_LABEL))
{code}
- getChildrenAllocationIterator -> sortAndGetChildrenAllocationIterator
> Queue sorting in CapacityScheduler should consider node label
> -------------------------------------------------------------
>
> Key: YARN-2696
> URL: https://issues.apache.org/jira/browse/YARN-2696
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: capacityscheduler, resourcemanager
> Reporter: Wangda Tan
> Assignee: Wangda Tan
> Attachments: YARN-2696.1.patch, YARN-2696.2.patch
>
>
> In the past, when trying to allocate containers under a parent queue in
> CapacityScheduler. The parent queue will choose child queues by the used
> resource from smallest to largest.
> Now we support node label in CapacityScheduler, we should also consider used
> resource in child queues by node labels when allocating resource.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
