rmadmin

-refreshQueues

Reloads the queues' acls, states, and scheduler-specific properties. ResourceManager will reload the mapred-queues configuration file

-refreshNodes [-g|graceful <timeout in seconds> -client|server]

Refreshes the hosts information at the ResourceManager. Here [-g|graceful <timeout in seconds> -client|server] is optional, if you specify the timeout, then ResourceManager will wait for the 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 setting the timeout to -1 indicates an infinite timeout.

Known Issue: the server-side tracking will immediately decommission if an RM HA failover occurs

-refreshNodesResources

Refreshes resources of NodeManagers at the ResourceManager

-refreshSuperUsrGroupsConfiguration

Refreshes superuser proxy groups mappings

-refreshUserToGroupsMappings

Refreshes user-to-groups mappings

-refreshAdminAcls

Refreshes ACLs (Accecc Control Lists) for administration of ResourceManager

-refreshServiceAcl

Reloads the service-level authorization policy file

-getGroups <username>

Returns groups the specified user belongs to

-addToCLusterNodeLabels <"label1(exclusive=true),label2(exclusive=false),label3">

Adds node labels to cluster. Default exclusivity is true

-removeFromClusterNodeLabels <label1,label2,label3> (label splitted by ",")

Removes from cluster node labels

-replaceLabelsOnNode <"node1[:port]=label1,label2 node2[:port]=label1,label2"> [-failOnUnknownNodes]

Replaces labels on nodes (specifying multiple labels on a single host is not supported for now). -failOnUnknownNodes is optional. When set, it will cause a failure if specified nodes are unknown

-directlyAccessNodeLabelStore

Deprecated, will be removed in future releases. Directly access node label store, with this option, all node label related operations will not connect ResourceManager. Instead, they will access/modify stored node labels directly. By default, it is set to false (access via Resource Manager).

If you configure yarn.node-labels.fs-store.root-dir to point to a local directory (instead of NFS or HDFS), this option will only work when the command runs on the machine where Resource Manager is running

-refreshClusterMaxPriority

Refreshes cluster maximum priority

-updateNodeResource [NodeID] [MemSize] [vCores] ([OvercommitTimeout])

Updates resource types on specific nodes. Resource types are comma-delimited key/value pairs of any resources available at Resource Manager. For example, memory-mb=1024Mi,vcores=1,resource1=2G,resource2=4m

-transitionToActive [-forceactive] [-forcemanual] <serviceId>

Transitions the service into active state. Try to make the target active without checking that there is no active node if the -forcemanual option is used. This command can not be used if automatic failover is enabled. Though you can override this by using -forcemanual option, use it with caution

-transitionToStandby [-forcemanual] <serviceId>

Transitions the service into the Standby state. This command cannot be used if automatic failover is enabled. Though you can override this by using -forcemanual option, use it with caution

-getServiceState <serviceId>

Returns the state of the specified service

-getAllServiceState

Returns the state of all services

-checkHealth <serviceId>

Requests the service to perform a health check. The RMAdmin tool will exit with a non-zero exit code if the check fails

-help [cmd]

Displays help for the given command or all commands if none is specified