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

Jian He commented on YARN-2694:
-------------------------------

one other comment: revert changes regarding checkAddLabelsToNode, given this 
method is currently not used at all. If it's used, it means we need to support 
multiple labels per node, meaning we need to revert this change again including 
the tests.

> Ensure only single node labels specified in resource request / host, and node 
> label expression only specified when resourceName=ANY
> -----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: YARN-2694
>                 URL: https://issues.apache.org/jira/browse/YARN-2694
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: capacityscheduler, resourcemanager
>            Reporter: Wangda Tan
>            Assignee: Wangda Tan
>         Attachments: YARN-2694-20141020-1.patch, YARN-2694-20141021-1.patch, 
> YARN-2694-20141023-1.patch, YARN-2694-20141023-2.patch, 
> YARN-2694-20141101-1.patch, YARN-2694-20141101-2.patch, 
> YARN-2694-20150121-1.patch, YARN-2694-20150122-1.patch, 
> YARN-2694-20150202-1.patch, YARN-2694-20150203-1.patch
>
>
> Currently, node label expression supporting in capacity scheduler is partial 
> completed. Now node label expression specified in Resource Request will only 
> respected when it specified at ANY level. And a ResourceRequest/host with 
> multiple node labels will make user limit, etc. computation becomes more 
> tricky.
> Now we need temporarily disable them, changes include,
> - AMRMClient
> - ApplicationMasterService
> - RMAdminCLI
> - CommonNodeLabelsManager



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

Reply via email to