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 Update

PDF
포커스 모드
폰트 크기
마지막 업데이트 시간: 2024-10-30 11:11:06

Overview

Configuration management supports the modification of key configuration parameters for commonly used open-source components such as HIVE and SPARK. You can modify the service configuration for different roles based on actual requirements. This document introduces the directions for configuring parameters through the console.
Note
When you delete custom configuration files in the console’s configuration management, for security reasons, the client will not synchronize the deletion action.

Directions

Editing Configuration

1. Log in to the EMR on TKE Console and click the Cluster ID/Name in the cluster list to enter the cluster details page.
2. On the cluster details page, select Cluster Services, and click the corresponding service to enter the Configuration Management page.
3. After the configuration management page is entered, select the desired role as needed.
4. If you want to search for a specific configuration item or narrow down the search scope, you can use the filter on the left side.
5. Select the configuration file as needed, click Edit Configuration to enter edit mode, and proceed with adding, editing, or deleting configuration items as required.
Select the parameter to be modified and enter the new parameter value. If it is necessary, click Restore to recover to the original value or Default Value to reset to the system-recommended default value.
Some parameters support deletion. To delete the configuration, select Delete > Confirm.
If the desired parameter is not present in the file, you can click Add Configuration Item to open the add configuration item pop-up, and fill in the parameter name and value.
6. After the information is confirmed, click Save Configuration. Once the configuration is successfully applied, click Restart Service to complete the configuration modification.
Description
Note If modifications are made to the service process configuration, a restart of the service is required after saving for the modifications to take effect.
If modifications are made to the client configuration, the modifications take effect immediately after saving, without restarting the service.

Adding Configuration File

1. Log in to the EMR on TKE Console and click the Cluster ID/Name in the cluster list to enter the cluster details page.
2. On the cluster details page, select Cluster Services, and click the corresponding service to enter the Configuration Management page.
3. If the desired configuration file is not available, click the + (Add Configuration File) on the right to enter the configuration file setup page and fill in the configuration details.
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. Custom configuration files, once effective, support modification and deletion operations.

도움말 및 지원

문제 해결에 도움이 되었나요?

피드백