MRS 2.1.0.2 Patch Description
Basic Information
Patch Version |
MRS 2.1.0.2 |
---|---|
Release Date |
2020-04-22 |
Resolved Issues |
List of the resolved issues in MRS 2.1.0.2: MRS Manager No monitoring information is displayed after NodeAgent is restarted. When a job is under submission for a long time, memory overflow occurs in the manager executor process. Job submission is supported. You can configure the concurrency for manager executor. New Kafka topics are not displayed on the MRS Manager management plane. When you call security cluster's APIs to submit the Spark Submit job and perform operations on an HBase table, the permission control on the HBase table does not take effect. The MRS Manager patch mechanism has been optimized. MRS big data components The slow running of the load data inpath command executed by Spark has been optimized. Column names containing the dollar sign ($) can be used in Spark table creation. OBS-related problems have been solved. |
List of the resolved issues in MRS 2.1.0.1: MRS Manager The return results of Hive SQL statements submitted by V2 jobs have been optimized, and the issue that V2 jobs fail to be submitted using an agency token has been solved. MRS big data components HiveServer out of memory (OOM) has been solved for MRS Hive: HIVE-10970 and HIVE-22275 |
|
Compatibility with Other Patches |
The MRS 2.1.0.2 patch package contains all content of the MRS 2.1.0.1 patch package. |
Impact of Patch Installation
- During the installation of the MRS 2.1.0.2 patch, MRS Manager will be restarted, and the components such as Hive, Spark, HDFS, Yarn, MapReduce, Presto, HBase, and related dependent services will be restarted in rolling mode. During the restart of MRS Manager, services are temporarily unavailable, and services are not interrupted during the rolling restart.
- After installing the MRS 2.1.0.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).
- For details about how to fully update the original client of the active Master node, see Fully Updating the Original Client of the Active Master Node.
- For details about how to fully update the original client of the standby Master node, see Fully Updating the Original Client of the Standby Master Node.
- For details about how to fully install the clients you set up, see Installing a Client (Versions Earlier Than 3.x).
- 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.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.