MRS 3.2.0-LTS.1 Patch Description
Basic information about MRS 3.2.0-LTS.1.6
Patch Version |
MRS 3.2.0-LTS.1.6 |
---|---|
Release Date |
2024-02-04 |
Pre-Installation Operations |
If an MRS cluster node is faulty or the network is disconnected, isolate the node first. Otherwise, the patch installation will fail. |
New Features |
|
Resolved Issues |
List of resolved issues in MRS 3.2.0-LTS.1.6:
|
Compatibility with Other Patches |
The MRS 3.2.0-LTS.1.6 patch package contains all patches for fixing single-point issues in MRS 3.2.0-LTS.1. |
Impact of Patch Installation |
Impact of Patch Installation
- During MRS 3.2.0-LTS.1 patch installation, OMS automatically restarts, which affects cluster management operations, such as job submission and cluster scaling. Install patch in off-peak hours.
- After the MRS 3.2.0-LTS.1.6 patch is installed or uninstalled, restart the Flink, Yarn, HDFS, MapReduce, Ranger, HetuEngine, Flume, Hive, Kafka, and Spark2x services on FusionInsight Manager for the patch to take effect. During restart, some services may be unavailable for a short period. To ensure service continuity, restart the components in off-peak hours. Before uninstalling the patch, log in to FusionInsight Manager, and choose System > Third-Party AD to disable AD interconnection.
- If a client is manually installed inside or outside the cluster, you need to upgrade or roll back the client.
- Log in to the active node of the cluster.
cd /opt/Bigdata/patches/{Patch version}/download/
In all operations, replace {Patch version} with that used in the real-life project. For example, if the installed patch is MRS_3.2.0-LTS.1.1, the value of {Patch version} is MRS_3.2.0-LTS.1.1.
- Copy the patch installation package to the /opt/ directory on the client node.
scp patch.tar.gz {IP address of the client node}:/opt/
The following shows an example.
scp patch.tar.gz 127.0.0.1:/opt/
- Log in to the node where the client is deployed.
The following shows an example.
ssh 127.0.0.1
- Run the following commands to create a patch directory and decompress the patch package:
tar -zxf /opt/patch.tar.gz -C /opt/{Patch version}
- Upgrade/Rollback a patch.
- Upgrade the patch on the client node.
Log in to the node where the client is deployed.
cd /opt/{Patch version}/client
sh upgrade_client.sh upgrade {Client installation directory}
The following shows an example.
sh upgrade_client.sh upgrade /opt/client/
- Roll back the patch on the client node (after the patch is uninstalled).
Log in to the node where the client is deployed.
cd /opt/{Patch version}/client
sh upgrade_client.sh rollback {Client installation directory}
The following shows an example.
sh upgrade_client.sh rollback /opt/client/
- Upgrade the patch on the client node.
- Log in to the active node of the cluster.
- If the Spark service is installed on MRS 3.2.0-LTS.1, upgrade the ZIP package in HDFS on the active OMS node after the patch is installed.
- Log in to the active node of the cluster.
cd /opt/Bigdata/patches/{Patch version}/client/
source /opt/Bigdata/client/bigdata_env
- Authenticate users who have permissions on HDFS on a cluster in security mode.
- Upgrade the package in HDFS.
- (Optional) Roll back upgrade after the patch is uninstalled.
- Log in to the active node of the cluster.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.