An Exception Occurs During Specifications Upgrade of Nodes in an MRS Cluster

Symptom

A component may fail to be started or encounter an exception after nodes specifications are upgraded. As a result, an exception occurs in the upgrade. The symptoms are as follows:

• The specifications of the failed node have been upgraded.

  

• A new specifications upgrade failure is displayed on the Manage Failed Tasks page.

  

• If IAM users have been synchronized, you can view abnormal roles on the Components page.

  

  If they are not synchronized, you can view abnormal roles on the Manager page of this cluster.

Cause Analysis

The failure is caused by the cluster component exception.

Procedure

• Method 1:
  1. Go to the Components page and check the service health status and operating status. If any service is not started, click the service to go to its details page.

     

  2. On the Instances page, select the instance that is not started, click More, and select Start Instance.

     

     

     If there are many abnormal roles, you can choose Start All Components from the Management Operations drop-down list.

     

• Method 2:

  Go to the Manager page of the cluster and check whether there are instances that are not started. If yes, start the instances.

  

• For other exceptions that cannot be resolved, contact technical support.