Help Center/ MapReduce Service/ Troubleshooting/ Cluster Management/ Some Instances Fail to Be Started After Core Nodes Are Added to the MRS Cluster
Updated on 2024-12-18 GMT+08:00
View PDF

Some Instances Fail to Be Started After Core Nodes Are Added to the MRS Cluster

Symptom

Cores nodes are added, but some instances on the nodes may fail to be started. The symptoms are as follows:

  1. A core node has been added and is displayed on the Nodes page.

  2. Some tasks for adding nodes fail or are partially successful.

  3. If IAM users have been synchronized, you can view unstarted roles on the Components page.
  4. If they are not synchronized, you can view unstarted roles on the Manager page of this cluster.

Procedure

Scenario 1: The task for adding nodes fails before component installation.

  1. Perform the following steps if the MRS cluster is a pay-per-use cluster:

    1. Log in to the MRS console.
    2. Choose Active Clusters and click the cluster name to go to the cluster details page.
    3. Click in the upper part of the page. In the Task List column, click the task for adding core nodes.
    4. Records all nodes in the verification request parameter.
    5. Click the Nodes tab, select the nodes recorded in 1.d, click Stop in the upper right corner, and stop the nodes as prompted.
    6. Reduce nodes by referring to Scaling In a Cluster.

  2. If the MRS cluster is billed on a yearly/monthly basis, unsubscribe from the abnormal nodes by referring to Unsubscribing from a Specified Node in a Yearly/Monthly Cluster.

Scenario 2: The task for adding nodes fails after component installation.

  1. Log in to the MRS console.
  2. Choose Active Clusters and click the cluster name to go to the cluster details page.
  3. On the Dashboard tab, click Synchronize next to IAM User Sync to synchronize IAM users.
  4. Click Components and check the role status of each service. If a role is not started, select the role, click More, and select Start Instance to start the instance.

  5. If the startup fails, rectify the fault based on the error information in the task list and try again.

    • If there are many abnormal roles, click Management Operations in the upper right corner to start all components.
    • For other exceptions that cannot be resolved, contact technical support.
    • You can also start the instance on the Manager page of the cluster. For details, see Overview

Parent topic: Cluster Management