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

Hudson commented on YARN-2970:
------------------------------

FAILURE: Integrated in Hadoop-trunk-Commit #6781 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/6781/])
YARN-2970. NodeLabel operations in RMAdmin CLI get missing in help command. 
(Contributed by Varun Saxena) (junping_du: rev 
e1ee0d45ea3315e7fbe1d28a7a35a0ce0c54483b)
* 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/test/java/org/apache/hadoop/yarn/client/cli/TestRMAdminCLI.java
* hadoop-yarn-project/CHANGES.txt
* 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/main/java/org/apache/hadoop/yarn/client/cli/RMAdminCLI.java


> NodeLabel operations in RMAdmin CLI get missing in help command.
> ----------------------------------------------------------------
>
>                 Key: YARN-2970
>                 URL: https://issues.apache.org/jira/browse/YARN-2970
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: api, client, resourcemanager
>    Affects Versions: 2.6.0
>            Reporter: Junping Du
>            Assignee: Varun Saxena
>            Priority: Minor
>             Fix For: 2.7.0
>
>         Attachments: YARN-2970.001.patch, YARN-2970.patch
>
>
> NodeLabel operations in RMAdmin CLI get missing in help command when I am 
> debugging YARN-313, we should add them on as other cmds:
> {noformat} 
> yarn rmadmin [-refreshQueues] [-refreshNodes] [-refreshResources] 
> [-refreshSuperUserGroupsConfiguration] [-refreshUserToGroupsMappings] 
> [-refreshAdminAcls] [-refreshServiceAcl] [-getGroup [username]] 
> [-updateNodeResource [NodeID] [MemSize] [vCores] ([OvercommitTimeout]) [-help 
> [cmd]]
>    -refreshQueues: Reload the queues' acls, states and scheduler specific 
> properties.
>                 ResourceManager will reload the mapred-queues configuration 
> file.
>    -refreshNodes: Refresh the hosts information at the ResourceManager.
>    -refreshResources: Refresh resources of NodeManagers at the 
> ResourceManager.
>    -refreshSuperUserGroupsConfiguration: Refresh superuser proxy groups 
> mappings
>    -refreshUserToGroupsMappings: Refresh user-to-groups mappings
>    -refreshAdminAcls: Refresh acls for administration of ResourceManager
>    -refreshServiceAcl: Reload the service-level authorization policy file.
>                 ResoureceManager will reload the authorization policy file.
>    -getGroups [username]: Get the groups which given user belongs to.
>    -updateNodeResource [NodeID] [MemSize] [vCores] ([OvercommitTimeout]): 
> Update resource on specific node.
>    -help [cmd]: Displays help for the given command or all commands if none 
> is specified.
>    -addToClusterNodeLabels [label1,label2,label3] (label splitted by ","): 
> add to cluster node labels
>    -removeFromClusterNodeLabels [label1,label2,label3] (label splitted by 
> ","): remove from cluster node labels
>    -replaceLabelsOnNode [node1:port,label1,label2 node2:port,label1,label2]: 
> replace labels on nodes
>    -directlyAccessNodeLabelStore: Directly access node label store, with this 
> option, all node label related operations will not connect RM. Instead, they 
> will access/modify stored node labels directly. By default, it is false 
> (access via RM). AND PLEASE NOTE: if you configured 
> yarn.node-labels.fs-store.root-dir to a local directory (instead of NFS or 
> HDFS), this option will only work when the command run on the machine where 
> RM is running.
> {noformat}



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

Reply via email to