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

MRS 1.9.0.6 Patch Description

Basic Information

Table 1 Basic information

Patch Version

MRS 1.9.0.6

Release Date

2020-05-20

Resolved Issues

List of resolved issues in MRS 1.9.0.6:

MRS Manager

MRS Manager supports scale-in of specified nodes in a yearly/monthly cluster.

MRS big data components

Solved the problem of slow response when HiveSE delivers SQL statements.

Supported the jobhistory query failure information interface.

Solved the problem that fine-grained permissions do not take effect.

Fixed the exception that occurs when Hive on Spark reads data.

Solved the problem that data volume increases when the Hive on mrs task is executed twice.

Solved the problem that the performance of some strings is poor when vector-based vectorized query is enabled in Hive.

List of resolved issues in MRS 1.9.0.5:

MRS Manager

Optimized the service restart process during configuration saving on MRS Manager.

Rectified the periodic backup failure on MRS Manager.

MRS big data components

Private patch of Ranger

Resolved the JVM Create GC thread failed issue of Yarn.

Added the HiveServer2 task stacking alarm.

Added the alarm indicating that the GC time of HiveServer HiveMetastore exceeds 5s.

Added the alarm indicating that HiveServer2 uncomment ZooKeeper.

Added the alarm indicating that Yarn tasks failed and the number of killed tasks exceeds 5 within 20 minutes.

Corrected time zone of Spark JobHistory.

Optimized MetaStore restart mechanism.

Resolved the HIVE-22771 open-source issue.

Resolved the Hive beeline log printing errors.

Corrected the number of active nodes displayed on the Yarn page.

Resolved the slow response of RM page display, which is caused by large number of RM threads.

Supported OBS monitoring.

Upgraded the OBS packages.

Resolved the issue that some data is not inserted when 10 data records are concurrently inserted into hive-jdbc.

Resolved the issue that Hive occasionally reports a Kryo deserialization failure.

Resolved the issue of Spark JobHistory memory leakage.

Resolved the issue that the application list cannot be displayed occasionally in Spark JobHistory.

List of resolved issues in MRS 1.9.0.3:

MRS Manager

Upgraded ARM JDK on MRS Manager.

Resolved the issue that the system disk is fully occupied by logs of the Core node on MRS Manager.

MRS big data components

Resolved the issue that the number of Ranger logs cannot be set, which may cause full disk occupation.

List of resolved issues in MRS 1.9.0.2:

MRS Manager

Resolved the mutual trust lost between some Core nodes in the cluster.

Resolved the issue that instances fail to be added after the patch is installed.

Resolved the issue that the rolling restart timeout interval of HiveServer cannot be modified on MRS Manager.

MRS big data components

Upgraded the OBS packages.

List of resolved issues in MRS 1.9.0.1:

MRS Manager

Resolved the issue that MRS Manager does not support rolling patch installation without restarting services.

MRS big data components

Resolved the issue that the OBS entrusted access frequency is not limited to 140 times within 5 minutes.

Resolved the issue that Kafka does not support open-source access.

Resolved the SPARK-27637 open-source issue.

Optimized the Hive rolling restart.

Upgraded the OBS packages.

Compatibility with Other Patches

The MRS 1.9.0.6 patch can resolve all problems that have been resolved by the MRS 1.9.0 patch.

Impact of Patch Installation

  • During the installation of the MRS 1.9.0.6 patch, MRS Manager will be restarted, and the components such as Hadoop, Hive, Spark, Kafka, Ranger, 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 installing the MRS 1.9.0.6 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.