[ https://issues.apache.org/jira/browse/YARN-3413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wangda Tan updated YARN-3413: ----------------------------- Attachment: YARN-3413.1.patch Attached ver.1 patch contains changes - Removed updateNodeLabel interface in ResourceManagerAdministrationProtocol and related records - Now parameter of addToClusterNodeLabels changed from String to NodeLabel which contains a boolean exclusive field. - RMAdminCLI can specify exclusive when -addToClusterNodeLabels Patch is large because there're some renames, actual logic change are simple. > Node label attributes (like exclusive or not) should be able to set when > addToClusterNodeLabels and shouldn't be changed during runtime > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: YARN-3413 > URL: https://issues.apache.org/jira/browse/YARN-3413 > Project: Hadoop YARN > Issue Type: Sub-task > Components: api, client, resourcemanager > Reporter: Wangda Tan > Assignee: Wangda Tan > Attachments: YARN-3413.1.patch > > > As mentioned in : > https://issues.apache.org/jira/browse/YARN-3345?focusedCommentId=14384947&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14384947. > Changing node label exclusivity and/or other attributes may not be a real use > case, and also we should support setting node label attributes whiling adding > them to cluster. -- This message was sent by Atlassian JIRA (v6.3.4#6332)