tencent cloud

Elastic MapReduce

Release Notes and Announcements
Release Notes
Announcements
Security Announcements
Product Introduction
Overview
Strengths
Architecture
Features
Use Cases
Constraints and Limits
Technical Support Scope
Product release
Purchase Guide
EMR on CVM Billing Instructions
EMR on TKE Billing Instructions
EMR Serverless HBase Billing Instructions
Getting Started
EMR on CVM Quick Start
EMR on TKE Quick Start
EMR on CVM Operation Guide
Planning Cluster
Administrative rights
Configuring Cluster
Managing Cluster
Managing Service
Monitoring and Alarms
TCInsight
EMR on TKE Operation Guide
Introduction to EMR on TKE
Configuring Cluster
Cluster Management
Service Management
Monitoring and Ops
Application Analysis
EMR Serverless HBase Operation Guide
EMR Serverless HBase Product Introduction
Quotas and Limits
Planning an Instance
Managing an Instance
Monitoring and Alarms
Development Guide
EMR Development Guide
Hadoop Development Guide
Spark Development Guide
Hbase Development Guide
Phoenix on Hbase Development Guide
Hive Development Guide
Presto Development Guide
Sqoop Development Guide
Hue Development Guide
Oozie Development Guide
Flume Development Guide
Kerberos Development Guide
Knox Development Guide
Alluxio Development Guide
Kylin Development Guide
Livy Development Guide
Kyuubi Development Guide
Zeppelin Development Guide
Hudi Development Guide
Superset Development Guide
Impala Development Guide
Druid Development Guide
TensorFlow Development Guide
Kudu Development Guide
Ranger Development Guide
Kafka Development Guide
Iceberg Development Guide
StarRocks Development Guide
Flink Development Guide
JupyterLab Development Guide
MLflow Development Guide
Practical Tutorial
Practice of EMR on CVM Ops
Data Migration
Practical Tutorial on Custom Scaling
API Documentation
History
Introduction
API Category
Cluster Resource Management APIs
Cluster Services APIs
User Management APIs
Data Inquiry APIs
Scaling APIs
Configuration APIs
Other APIs
Serverless HBase APIs
YARN Resource Scheduling APIs
Making API Requests
Data Types
Error Codes
FAQs
EMR on CVM
Service Level Agreement
Contact Us

Configuration Management

PDF
フォーカスモード
フォントサイズ
最終更新日: 2023-12-27 14:12:56

Overview

Configuration management allows you to modify key configuration parameters of popular open-source components like HDFS, YARN, Hive, and Spark. The configuration of services can be modified as needed at the level of cluster, node, or configuration group. This document describes how to configure service parameters in the console.
Caution
For security reasons, when a custom configuration file is deleted in Configuration Management in the console, it will not be deleted from the client.
If you need to delete a custom configuration file from the client, you can use a cluster script to batch perform the operation on existing clusters.
After configuration modification, if the configuration status in Role Management changes to Configuration expired, you need to restart the service to make the configuration effective.

Directions

Editing a configuration item

1. Log in to the EMR console, select the target cluster in the cluster list, and click Service to enter the cluster service list.
2. In the cluster service list, select Operation > Configuration Management in the top-right corner of the target service panel.


3. On the Configuration Management page, select the Level as needed. By default, Cluster level is selected.
To configure the parameters of all nodes of the selected service in the cluster, select Cluster level.
To configure the parameters of multiple specified nodes of the selected service, create a configuration group and use it as the level.
To configure the parameters of a specified node of the selected service, select Node level.

4. You can search for a configuration item or narrow down the search scope with the filter on the left.
5. Select the target configuration file, click Edit Configuration, and perform operations such as adding, editing, and deleting configuration items as needed.
Enter the new parameter value for the target parameter. If needed, you can click Recover to recover a parameter to its original value. You can also click Default Value to restore the parameter to the default value recommended by the system.
You can delete certain configuration items by clicking Delete > OK.
If the file does not have the parameter you want to configure, click Add a configuration item and enter the new parameter name and value in the pop-up window.
6. After confirming that the modification is correct, click Save configuration. After the configuration is delivered successfully, click Restart Service.
Note
If the service process configuration is modified, the configuration will not take effect unless you restart the service.
If the client configuration is modified, the configuration will take effect immediately after being saved.

Adding a configuration file

1. Log in to the EMR console, select the target cluster in the cluster list, and click Service to enter the cluster service list.
2. In the cluster service list, select Operation > Configuration Management in the top-right corner of the target service panel.
3. If the configuration file you want to configure does not exist, you can click Add configuration file on the right to configure a configuration file.
4. After you click Save configuration, the parameters will be delivered, and the configuration file name will be updated in the configuration file list.


5. After the custom configuration file is delivered and takes effect, it can be modified and deleted.

Comparing configurations at different levels

After configurations are modified at different levels, click Switch to dimension-based comparisons to compare them at the cluster, configuration group, and node levels. To make the configuration at a level the same as that at the higher level, overwrite the difference and save the modification.



ヘルプとサポート

この記事はお役に立ちましたか?

フィードバック