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

Vinod Kumar Vavilapalli commented on YARN-3345:
-----------------------------------------------

Just looked at this. I think UpdateNodeLabels can be used to also change the 
exclusivity of an existing label - which may or may not be something that is a 
real use-case. I think we should have the APIs to create labels with the right 
properties at creation time itself.

> Add non-exclusive node label API to RMAdmin protocol and NodeLabelsManager
> --------------------------------------------------------------------------
>
>                 Key: YARN-3345
>                 URL: https://issues.apache.org/jira/browse/YARN-3345
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: api, client, resourcemanager
>            Reporter: Wangda Tan
>            Assignee: Wangda Tan
>             Fix For: 2.8.0
>
>         Attachments: YARN-3345.1.patch, YARN-3345.2.patch, YARN-3345.3.patch, 
> YARN-3345.4.patch, YARN-3345.5.patch, YARN-3345.6.patch, YARN-3345.7.patch
>
>
> As described in YARN-3214 (see design doc attached to that JIRA), we need add 
> non-exclusive node label RMAdmin API and CLI implementation.



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

Reply via email to