[ https://issues.apache.org/jira/browse/YARN-3581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14529962#comment-14529962 ]
Naganarasimha G R commented on YARN-3581: ----------------------------------------- Hi [~wangda] There was one trivial issue with the CLI, can you take care of that as part of this patch: we are mentioning in help for {{yarn rmadmin}} {{-addToClusterNodeLabels \[label1(exclusive=true),label2(exclusive=false),label3\]}} but its not captured that : if not specified then default exclusive=true > Deprecate -directlyAccessNodeLabelStore in RMAdminCLI > ----------------------------------------------------- > > Key: YARN-3581 > URL: https://issues.apache.org/jira/browse/YARN-3581 > Project: Hadoop YARN > Issue Type: Sub-task > Components: api, client, resourcemanager > Reporter: Wangda Tan > Assignee: Wangda Tan > > In 2.6.0, we added an option called "-directlyAccessNodeLabelStore" to make > RM can start with label-configured queue settings. After YARN-2918, we don't > need this option any more, admin can configure queue setting, start RM and > configure node label via RMAdminCLI without any error. > In addition, this option is very restrictive, first it needs to run on the > same node where RM is running if admin configured to store labels in local > disk. > Second, when admin run the option when RM is running, multiple process write > to a same file can happen, this could make node label store becomes invalid. -- This message was sent by Atlassian JIRA (v6.3.4#6332)