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

Wangda Tan updated YARN-3345:
-----------------------------
    Attachment: YARN-3345.5.patch

bq. public/unstable annotations for the newly added records, e.g. 
SetNodeLabelsAttributesRequest, 
Done 

bq. NodeLabelAttributes -> NodeLabel, so that AddToClusterNodeLabelsRequest can 
later on use the same data structure.
Done 

bq. for node exclusiveness - I think we may use NodeLabel#(get/set)IsExclusive
Done 

bq. “ an un existed node-label=%s” - “non-existing node-label”
Done

bq. throw YarnException instead of IOException
Done

bq. below code, how about user wants to set the attributes to be empty if 
(attr.getAttributes().isEmpty()) {
  // simply ignore
  continue;
}
Done, removed map of attributes, added top level "shareable"

bq. add a newInstance method in SetNodeLabelsAttributesResponse and use that
Done

bq. revert RMNodeLabelsManager change
There're some renames, so we cannot revert RMNodeLabelsMgr changes.

> Add non-exclusive node label RMAdmin CLI/API
> --------------------------------------------
>
>                 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
>         Attachments: YARN-3345.1.patch, YARN-3345.2.patch, YARN-3345.3.patch, 
> YARN-3345.4.patch, YARN-3345.5.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