YARN service management via ADCM
The ADCM UI provides actions to manage the YARN service and its components. For information on how to run service actions, refer to ADH service actions.
The actions available for the YARN service are listed in the table below.
For more information about YARN components, see YARN architecture.
| Action | Description |
|---|---|
Check |
Runs service-specific tests to check the health of the service and its components |
Start |
Starts the service.
When you run this action, the option Apply configs from ADCM is available.
If it is set to |
Stop |
Stops the service |
Restart |
Restarts the service.
When you run this action, the option Apply configs from ADCM is available.
If it is set to |
Remove |
Removes the service from the cluster.
This action should be used to remove already installed services.
Whereas the |
Add Client(s) |
Adds YARN client(s) to the cluster. Running this action opens the component-host mapping interface where you can add new YARN clients |
Remove Client(s) |
Removes YARN client(s) from cluster hosts. Running this action opens the component-host mapping interface where you can remove YARN clients from specific hosts |
Move MapReduce History Server |
Moves the MapReduce History Server component to a different cluster host. Use the force option if the source host (where the component is currently installed) is offline |
Move ResourceManagers Server |
Moves the YARN ResourceManagers Server component to a different cluster host. Use the force option if the source host (where the component is currently installed) is offline |
Move YARN Timeline Server |
Moves the YARN Timeline Server component to a different cluster host. Use the force option if the source host (where the component is currently installed) is offline |
Add NodeManagers |
Adds YARN NodeManagers. Running this action opens the component-host mapping interface where you can add new NodeManagers |
Decommiss NodeManagers |
Shuts down a NodeManager. This action can be used to temporarily take a node out of service or safely delete it. When using this action, enter the FQDNs of the hosts to decommission and the time to start the decommission in seconds (Timeout). The decommission is immediate by default. To decommission a node gracefully, use the |
Recommiss NodeManagers |
Reinstates the decommissioned NodeManagers |
Remove NodeManagers |
Removes YARN NodeManagers. Running this action opens the component-host mapping interface where you can remove NodeManagers |
Manage Ranger plugin |
Enables or disables Ranger plugin for YARN |
Add ResourceManager(s) |
Adds YARN ResourceManager components. Running this action opens the component-host mapping interface where you can add new ResourceManager components. For more information on ResourceManager, see YARN high availability overview |
Add/modify node labels |
Adds or changes node labels. You can use node labels to create groups of hosts, for example, to designate nodes to specific tasks or to manage nodes' resources between queues. When using this action, enter labels to be used in a cluster and their exclusivity ( |
Add/modify node-to-labels mapping |
Maps the node labels added using the Add/modify node labels action to the hosts. When using this action, enter the hosts' FQDNs and the labels you want to assign to them |
Reload Scheduler config |
Reloads access control lists, states, and scheduler specific properties. Use this action to apply changes made to Capacity Scheduler’s configuration file. Fair Scheduler doesn’t require reloading after its configuration has been altered |
Remove node label |
Removes node labels from the cluster. When using this action, enter the list of labels you want to remove separated by commas |
Remove ResourceManagers |
Removes YARN ResourceManager components. Running this action opens the component-host mapping interface where you can remove ResourceManager components |
