Updated on 2023-05-15 GMT+08:00

MRS 1.9.2.2 Patch Description

Basic Information

Table 1 Basic information

Patch Version

MRS 1.9.2.2

Release Date

2021-05-18

Resolved Issues

MRS Manager

Resolved the sudo privilege escalation vulnerability.

Resolved the issue of queue information loss due to queue update during capacity expansion.

MRS big data components

Resolved the issue that the Hive on Spark task is suspended because the block ID is displayed as garbled characters.

Self-developed APIs are added to Hive.

Resolved the issue that the map.xml file cannot be read.

Optimized the Hive Har feature.

Resolved the issue that Yarn is unavailable due to ZooKeeper dirty data.

Upgraded the OBS packages.

Upgraded the JDK version.

Resolved the issue of ResourceManager memory leakage.

Added the monitoring on the exception that occurs when the ECS getSecuritykey API is called.

Optimized the temporary AK/SK process.

Resolved the issue of ResourceManager memory leakage.

Fixed the error reported when the Hive union statement is used to merge small files.

Resolved the issue that the Hadoop task fails to be executed due to insufficient space.

Resolved the issue that no data is generated after a Hive job is successfully executed.

Compatibility with Other Patches

None

Impact of Patch Installation

  • During the installation of the MRS 1.9.2.2 patch, MRS Manager will be restarted, and the components such as Hadoop, Hive, Spark, Kafka, Ranger, Presto, and related dependent services will be restarted in rolling mode. During the restart of MRS Manager, services are temporarily unavailable but services are not interrupted during the rolling restart.
  • After the MRS 1.9.2.2 patch is installed, you need to restart the OMS service.
    • Log in to the active and standby OMS nodes as user root, switch to user omm, and run the sh ${BIGDATA_HOME}/om-0.0.1/sbin/restart-oms.sh command to restart the OMS service.
    • Both the active and standby OMS nodes need to be restarted.
  • After installing the MRS 1.9.2.2 patch, you need to download and install all clients again, including the original clients of Master nodes and the clients used by other nodes of VPC (that is, the clients that you set up).
    • You are advised to back up the old clients before reinstalling the new ones.
    • If you have modified client configurations based on the service scenario, modify them again after reinstalling the clients.