How Do I Check the ResourceManager Configuration of Yarn?

This section applies only to versions earlier than MRS 3.x.

1. Log in to MRS Manager and choose Services > Yarn > Instance.
2. Click the names of the two ResourceManager nodes, choose More > Synchronize Configuration, and deselect Restart services or instances whose configurations have expired. .
   Figure 1 Synchronizing the configuration
   

3. Click Yes to synchronize the configuration.
4. Log in to the Master nodes as user root.
5. Run the cd /opt/Bigdata/MRS_Current/*_*_ResourceManager/etc_UPDATED/ command to go to the etc_UPDATED directory.
6. Run the grep '\.queues' capacity-scheduler.xml -A2 command to display all configured queues and check whether the queues are consistent with those displayed on Manager.

   root-default is hidden on the Manager page.

   

7. Run the grep '\.capacity</name>' capacity-scheduler.xml -A2 command to display the value of each queue and check whether the value of each queue is the same as that displayed on Manager. Check whether the sum of the values configured for all queues is 100.
   • If the sum is 100, the configuration is correct.
   • If the sum is not 100, the configuration is incorrect. Perform the following steps to rectify the fault.

   

8. Log in to MRS Manager, and select Hosts.
9. Determine the active Master node. The host name of the active Master node starts with a solid pentagon.
10. Log in to the active Master node as user root.
11. Run the su - omm command to switch to user omm.
12. Run the sh /opt/Bigdata/om-0.0.1/sbin/restart-controller.sh command to restart the controller when no operation is being performed on Manager.

    Restarting the controller will not affect the big data component services.

13. Repeat 1 to 7 to synchronize ResourceManager configurations and check whether the configurations are correct.

    If the latest configuration has not been loaded after the configuration synchronization is complete, a message will be displayed on the Manager page indicating that the configuration has expired. However, this will not affect services. The latest configuration will be automatically loaded when the component restarts.