Scaling Up Master Node Specifications

Prerequisites

• You have checked whether the Host Security Service (HSS) is enabled. If HSS is enabled, disable the HSS monitoring on the MRS cluster before you scale up master node specifications.
• Ensure that sufficient specification resources are available throughout the steps in Scaling Up Master Node Specifications (Step-by-Step Upgrade).

Use Restrictions

• Master nodes can be scaled up for clusters with two or more master nodes.
• The specifications of the Master node in a BMS cluster cannot be upgraded.
• For MRS 1.8.2 or later to a version earlier than MRS 3.x or MRS 3.1.0 or later, see Scaling Up Master Node Specifications (One-Click Upgrade).
• For MRS 3.0.5 and a version earlier than MRS 1.8.2, see Scaling Up Master Node Specifications (Step-by-Step Upgrade).
• Do not perform other operations on the cluster during the scale-up.

Scaling Up Master Node Specifications (One-Click Upgrade)

1. Log in to the MRS console.
2. In the left navigation pane, choose Clusters > Active Clusters, select the cluster for which you want to scale up Master node specifications, and click its name to switch to the cluster details page.
3. On the Nodes tab page, select Scale Up Specifications in the Operation column of the Master node group. The Scale Up Master Node Specifications page is displayed.

   

4. Select the target specifications and click Submit Order. The order has been submitted successfully.
   The node specification scale-up takes some time. After the scale-up is successful, the cluster status changes to Running.

   

   • The VM to be scaled up is automatically stopped during the scale-up and started after the scale-up is complete.
   • The scale-up does not automatically upgrade the memory of components due to different component usage requirements. You can adjust the memory of components as needed.

Scaling Up Master Node Specifications (Step-by-Step Upgrade)

Preparing for Scaling Up Master Node Specifications

1. Log in to the MRS console.
2. In the left navigation pane, choose Clusters > Active Clusters, select the cluster for which you want to scale up Master node specifications, and click its name to switch to the cluster details page.
3. Ensure that the cluster status is Running.
4. On the Nodes tab page, ensure that all nodes in the cluster are in the Running state.
5. Log in to Manager and go to the cluster management page. For details, see Acceso a MRS Manager (MRS 2.x o anterior).
6. Choose Cluster > Services > ZooKeeper > Dashboard and ensure that Running Status of the ZooKeeper service is Normal.
   Figura 1 ZooKeeper service status
   

7. Update service parameter settings as required. For details, see Configuración de parámetros de servicio.
   

   You need to perform this step only once before scaling up the standby Master node.

8. Choose Cluster > Services > HDFS > Instance.
9. Record the business IP address of NameNode (Standby). When upgrading the specifications of the active Master node, record the business IP address of NameNode (Active). Figura 2 shows the location of the business IP address.
   Figura 2 Business IP address of the NameNode
   
   

   Only when the cluster is an analysis cluster, you can perform 8 to 9 to record the IP addresses of the active and standby nodes.

10. On the upper right of the Manager page, check the number next to the icon. If the number is 0, there is no running tasks in the cluster.
11. Click Hosts. If the cluster is an analysis cluster, select the checkbox of the host corresponding to the business IP address of the NameNode recorded in 9. If the cluster is a streaming cluster, you do not need to distinguish the active and standby nodes. You only need to choose hosts for the scale-up.
12. Choose More > Stop All Instances and wait until all instances are stopped.
    

    • When the node where Manager resides is scaled up, Manager may not be accessed due to an active/standby switchover. It is a normal phenomenon. Try to log in to Manager later. If the login fails for a long time, contact O&M personnel.
    • After all roles are stopped, the following alarms may be generated. After the scale-up of Master node specifications is complete and all roles are started, the alarms are automatically cleared.
      • ALM-12006 Falla de nodo
      • ALM-12010 Interrupción del latido del corazón de Manager entre los nodos activo y en espera
      • ALM-12039 Bases de datos de OMS activas/en espera no sincronizadas
      • ALM-14000 Servicio HDFS no disponible
      • ALM-14010 El servicio NameService es anormal
      • ALM-14012 El JournalNode no está sincronizado
      • ALM-16004 Servicio Hive no disponible
      • ALM-18000 Servicio de Yarn no disponible
      • ALM-19000 Servicio HBase no disponible
      • ALM-20002 Servicio de Hue no disponible
      • ALM-27001 DBService no disponible
      • ALM-27003 La interrupción del latido del corazón entre los nodos activo y en espera de DBService
      • ALM-27004 Incoherencia de datos entre DBServices activos y en espera
      • ALM-43001 Servicio Spark2x no disponible

Scaling Up Master Node Specifications

1. Log in to the MRS console.
2. In the left navigation pane, choose Clusters > Active Clusters, select the cluster for which you want to scale up Master node specifications, and click its name to switch to the cluster details page.
3. On the Nodes tab page, select Scale Up Specifications in the Operation column of the Master node group.
4. Select the target specifications and click Next.
   

   Ensure that target specification resources are sufficient. Otherwise, the active node cannot be scaled up.

5. On the Confirm page that is displayed, confirm the target node specifications and fees and click OK.
6. Ensure that all services on the standby Master node have been stopped. For operation details, refer to 1 to 12 in the Preparing for Scaling Up Master Node Specifications part. On the Scale Up Master Node Specifications page, select Are you sure you have stopped all services on the standby Master node? and If not all services are stopped before the scale-up, data saving failure or data damage may occur. and click Submit Order.
7. On the Warning page that is displayed, confirm again that all services on the standby Master node are stopped and click OK to start scaling up the specifications of the standby Master node.

   The node specification scale-up takes some time. Please wait. After the scale-up is successful, the cluster status changes to Scaled-up-first. Otherwise, contact O&M personnel.

8. After the standby Master node has been scaled up successfully, start all services and set parameters on the standby Master node by referring to 1 to 11 in the Operations After the Master Node Specifications Scale-up part.
9. After the services on the standby Master node are started, perform an active/standby NameNode switchover. Perform this step only for an analysis cluster and skip this step for a streaming cluster.
   1. Access the NameNode web UI of the active and standby nodes separately. For details about how to access the NameNode web UI, see 11.
   2. In the navigation bar on the NameNode web UI, choose Overview and record the NameNode IDs of the active and standby nodes. Do not close the page after recording.
      Figura 3 NameNode ID of the active node
      
   3. Log in to the ECS of any Master node and run the following command to configure environment variables:

      source /opt/Bigdata/client/bigdata_env

   4. If the Kerberos authentication is enabled for the current cluster, run the following command to authenticate the user. If the Kerberos authentication is disabled for the current cluster, skip this step.

      kinit MRS cluster user

      For example, kinit admin.

   5. Run the following command to perform an active/standby NameNode switchover:

      hdfs haadmin -failover <NameNode ID of the active node> <NameNode ID of the standby node>

   6. Go to the NameNode web UI page that is not closed in 9.b and refresh the page. You can view that the active/standby NameNode switchover is complete.
      Figura 4 NameNode
      

10. Stop all services on the active Master node by referring to 1 to 12 in the Preparing for Scaling Up Master Node Specifications part.
11. On the Scale Up Master Node Specifications page, select I confirm that all services on the standby Master node have been started. and I confirm that all services on the active Master node have been stopped, and click Submit.
12. On the Confirm page that is displayed, confirm again that all services on the active Master node are stopped and click OK to start scaling up the specifications of the active Master node.

    The node specification scale-up takes some time. Please wait. After the scale-up is successful, the cluster status changes to Scaled-up-success. Otherwise, contact O&M personnel.

13. Start all services and set parameters on the active Master node by referring to 1 to 11 in the Operations After the Master Node Specifications Scale-up part.
14. On the Scale Up Master Node Specifications page, select Are you sure you have started all services on the active Master node? and click OK to complete the scale-up.

Operations After the Master Node Specifications Scale-up

1. Log in to Manager and go to the cluster management page. For details, see Acceso a MRS Manager (MRS 2.x o anterior).
2. Click Hosts. Check basic information about the host corresponding to the business IP address of the NameNode recorded in 9 in the Preparing for Scaling Up Master Node Specifications part. If the Running Status is Good and Disk, Memory, and CPU have values, perform 9. If any of the preceding conditions is not met, go to the next step.
3. Log in to the standby Master node remotely. For details, see Inicio de sesión en un ECS.
4. Run the following command to switch to user omm:

   su - omm

5. Run the following command to start the Agent:

   sh /opt/Bigdata/nodeagent/bin/start-agent.sh

6. Run the following command to check whether the Agent is started successfully:

   jps | grep NodeAgent

7. Log in to Manager and go to the cluster management page. For details, see Acceso a MRS Manager (MRS 2.x o anterior).
8. Click Hosts. Check basic information about the host corresponding to the business IP address of the NameNode recorded in 9 in the Preparing for Scaling Up Master Node Specifications part to ensure that Running Status is Good and Disk, Memory, and CPU have values.
   

   It may take 3 minutes until the host status is normal after the Agent is started successfully. Please wait. If the host status is abnormal for a long time, contact O&M personnel.

9. On the Manager page, click Hosts and select the checkbox of the host corresponding to the business IP address of the NameNode recorded in 9 in the Preparing for Scaling Up Master Node Specifications part.
10. Choose More > Start All Instances and wait until all instances are started.
11. Access the NameNode web UI and check the NameNode startup status.
    1. On FusionInsight Manager, choose Cluster > Services > HDFS > Dashboard.
    2. In the HDFS Summary column, click NameNode of the active or standby node that has been scaled up on the right of NameNode Web UI.
    3. Go to the NameNode Web UI page, choose Startup Progress in the navigation bar. After ensuring that Percent Complete is displayed as 100%, go to the next step, as shown in Figura 5.
       Figura 5 NameNode startup status
       
    

    Perform 11 for an analysis cluster and skip this step for a streaming cluster.