Updating Encryption Keys of an MRS Cluster
When you install a cluster, the system generates an encryption key automatically to protect the security information stored in the cluster, such as database user passwords and key file access passwords. If you need to change the encryption key for any reason, such as if the original key is compromised or you want to rotate the key periodically, you can update it manually.
Impact on the System
- After a cluster key is updated, a new key is generated randomly in the cluster. This key is used to encrypt and decrypt the newly stored data. The old key is not deleted, and it is used to decrypt data encrypted using the old key. After security information is modified, for example, a database user password is changed, the new password is encrypted using the new key.
- When the key is updated, the cluster is stopped and cannot be accessed.
Prerequisites
- You have obtained the IP addresses of the active and standby management nodes.
- You have stopped the upper-layer service applications that depend on the cluster.
Updating an MRS Cluster Key (MRS 3.x or Later)
- Log in to FusionInsight Manager.
- Choose Cluster > Overview > More > Stop (for MRS 3.3.0 or later, choose More > Stop in the upper right corner on the Homepage). In the displayed dialog box, enter the password for the current login user.
Click OK. Wait until the system displays a message indicating that the cluster is successfully stopped.
- Log in to the active management node as user omm.
- Run the following command to disable logout upon timeout:
TMOUT=0
After the operations in this section are performed, 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.
- Run the following command to switch the directory:
cd ${BIGDATA_HOME}/om-server/om/tools
- 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):
The key is updated successfully if the following information is displayed:
Step 4-1: The key save path is obtained successfully. ... Step 4-4: The root key is sent successfully.
- On FusionInsight Manager, click Cluster, click the name of the desired cluster, and click Start. (For MRS 3.3.0 or later, choose More > Start in the upper right corner of the homepage.)
In the displayed dialog box, click OK. Wait until a message is displayed indicating that the startup is successful.
Updating an MRS Cluster Key (MRS 2.x or Earlier)
- Log in to MRS Manager and choose Services > More > Stop Cluster.
In the displayed dialog box, select I have read the information and understand the impact. Click OK. Wait until the system displays a message indicating that the operation is successful. Click Finish. The cluster is stopped successfully.
- Log in to the active management node.
- Run the following commands to switch the user:
sudo su - omm
- Run the following command to disable logout upon timeout:
TMOUT=0
- Run the following command to switch the directory:
cd ${BIGDATA_HOME}/om-0.0.1/tools
- 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):
The key is updated successfully if the following information is displayed:
... Step 4-1: The key save path is obtained successfully. ... Step 4-4: The root key is sent successfully.
- On MRS Manager, choose Services > More > Start Cluster.
In the displayed dialog box, click OK. After Operation successful is displayed, click Finish. The cluster is started.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot