Updating a Key for a Cluster

Scenario

When a cluster is installed, an encryption key is generated automatically by the system so that the security information in the cluster (such as all database user passwords and key file access passwords) can be stored in encryption mode. After the cluster is installed, if the original key is accidentally disclosed or a new key is required, you can manually update the key.

Impact on the System

Prerequisites

Procedure

  1. Log in to FusionInsight Manager.
  2. Choose Cluster > Name of the desired cluster and click Stop. In the dialog box that is displayed, enter the password of the current user

    and click OK. Wait for a while until a message indicating that the operation is successful is displayed.

  3. Log in to the active management node as user omm.
  4. Run the following command to disable logout upon timeout:

    TMOUT=0

    After the operations in this section are complete, run the TMOUT=Timeout interval command to restore the timeout interval in a timely manner. For example, TMOUT=600 indicates that a user is logged out if the user does not perform any operation within 600 seconds.

  5. Run the following command to go to the related directory:

    cd ${BIGDATA_HOME}/om-server/om/tools

  6. Run the following command to update the cluster key:

    sh updateRootKey.sh

    Enter y as prompted.

    The root key update is a critical operation. 
    Do you want to continue?(y/n):     

    If the following information is displayed, the key is updated successfully.

    Step 4-1: The key save path is obtained successfully. 
    ... 
    Step 4-4: The root key is sent successfully.     

  7. On FusionInsight Manager, click Cluster, click the name of the desired cluster, and click Start.

    In the displayed dialog box, click OK. Wait until a message is displayed, indicating that the startup is successful.