[jira] [Created] (YARN-5891) yarn rmadmin -help contains a misspelled ResourceManager

["Grant Sohn (JIRA)" <ji...@apache.org>]

Grant Sohn created YARN-5891:
--------------------------------

             Summary: yarn rmadmin -help contains a misspelled ResourceManager
                 Key: YARN-5891
                 URL: https://issues.apache.org/jira/browse/YARN-5891
             Project: Hadoop YARN
          Issue Type: Bug
          Components: resourcemanager
    Affects Versions: 2.6.0
            Reporter: Grant Sohn
            Priority: Trivial


In the refreshServiceAcl section.

{noformat}
rmadmin is the command to execute YARN administrative commands.
The full syntax is: 

yarn rmadmin [-refreshQueues] [-refreshNodes [-g [timeout in seconds] -client|server]] [-refreshSuperUserGroupsConfiguration] [-refreshUserToGroupsMappings] [-refreshAdminAcls] [-refreshServiceAcl] [-getGroup [username]] [-help [cmd]]

   -refreshQueues: Reload the queues' acls, states and scheduler specific properties. 
		ResourceManager will reload the mapred-queues configuration file.
   -refreshNodes [-g [timeout in seconds] -client|server]: Refresh the hosts information at the ResourceManager. Here [-g [timeout in seconds] -client|server] is optional, if we specify the timeout then ResourceManager will wait for timeout before marking the NodeManager as decommissioned. The -client|server indicates if the timeout tracking should be handled by the client or the ResourceManager. The client-side tracking is blocking, while the server-side tracking is not. Omitting the timeout, or a timeout of -1, indicates an infinite timeout.
   -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.
   -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.


Generic options supported are
-conf <configuration file>     specify an application configuration file
-D <property=value>            use value for given property
-fs <local|namenode:port>      specify a namenode
-jt <local|resourcemanager:port>    specify a ResourceManager
-files <comma separated list of files>    specify comma separated files to be copied to the map reduce cluster
-libjars <comma separated list of jars>    specify comma separated jar files to include in the classpath.
-archives <comma separated list of archives>    specify comma separated archives to be unarchived on the compute machines.

The general command line syntax is
bin/hadoop command [genericOptions] [commandOptions]
{noformat}





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

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org