tencent cloud

Elastic MapReduce

  • Release Notes and Announcements
  • Product Introduction
  • Purchase Guide
    • EMR on CVM Billing Instructions
    • EMR on TKE Billing Instructions
    • EMR Serverless HBase Billing Instructions
    • EMR Serverless TCBase Billing Overview
  • Getting Started
  • EMR on CVM Operation Guide
    • Planning Cluster
    • Administrative rights
    • Configuring Cluster
    • Managing Cluster
    • Managing Service
    • Monitoring and Alarms
    • TCInsight
  • EMR on TKE Operation Guide
  • EMR Serverless HBase Operation Guide
  • EMR Serverless TCBase Operation 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
    • 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
    • Making API Requests
    • Cluster Resource Management APIs
    • Cluster Services APIs
    • User Management APIs
    • Information Query APIs
    • Scaling APIs
    • Configuration APIs
    • Other APIs
    • Cluster Lifecycle APIs
    • Serverless HBase APIs
    • YARN Resource Scheduling APIs
    • Data Types
    • Error Codes
  • FAQs
    • EMR on CVM
  • Service Level Agreement
  • Contact Us

Modifying Configuration

Download
Mode fokus
Ukuran font
Terakhir diperbarui: 2024-10-30 10:59:06

Overview

When the service role CPU or memory is insufficient, you can increase the CPU or memory size by changing the configuration. This document introduces the relevant operations for changing instance configurations through the EMR on TKE console.
Note
Changing the configuration may cause running jobs to fail. Ensure that you perform this operation without impacting business operations.
During the configuration change process, resources may be preempted, causing pod reconstruction to fail and resulting in service unavailability. It is recommended to perform this operation during off-peak business hours.

Prerequisites

1. Pod resource configuration adjustments will be automatically billed item by item. Ensure sufficient account balance.
2. After the configuration of pay-as-you-go nodes is changed, the fees will be refrozen based on the latest configuration price. For more details, see EMR on TKE Billing Instructions > Purchase Instructions.

Directions

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 > A Certain Service, and enter the role management page.
3. On the role management page, select the service role that requires configuration changes and click Modify Configuration.
4. On the configuration adjustment page, confirm the relevant information for the configuration change, select the target CPU and memory configurations, and make sure to carefully read the important notice before checking Agree to Change Information.



Bantuan dan Dukungan

Apakah halaman ini membantu?

masukan