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

Scaling Out Cloud System Disks

PDF
포커스 모드
폰트 크기
마지막 업데이트 시간: 2026-03-20 15:54:33

Feature Introduction

If the original system disk capacity of the nodes in the cluster becomes insufficient as your business needs grow, a scale-out operation is required. This topic describes how to scale out cloud system disks in the EMR console.
Note:
You can scale out only cloud system disks. Local disks do not support scale-out.
Local disk models, pods, shared resource nodes, and underwriting billing nodes do not support scaling out cloud system disks.
Disks can only be scaled out and not scaled in to prevent data loss.
When batch scaling out the multi-node cloud system disk, you can perform operations in batches for nodes with the same billing mode, availability zone, or node type.

Operation Steps

1. Log in to the EMR console and click the corresponding Cluster ID/Name in the cluster list to go to the cluster details page.
2. Enter the resource management page and select the single-node operation or batch operation solution as needed:
2.1 Single-Node Cloud System Disk Scale-Out: Select the node to be scaled out and select More > Disk Adjustment > Scale Out Cloud System Disk in the Operation column of the list and enter the cloud system disk scale-out configuration page.
2.2 Multi-Node Cloud System Disk Batch Scale-Out: Select Disk Adjustment > Scale Out Cloud System Disk under the More Operations header and enter the cloud system disk scale-out configuration page.
3. Set the Unified Target Capacity, which should be greater than the current capacity. After the adjustment, the selected system disk will be resized to the specified capacity.
4. After confirming the information is correct, click OK to start scaling out the cloud system disks.
5. After the disk scale-out, the partition and file system will be scaled out automatically, and you do not need to perform a manual update.

도움말 및 지원

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

피드백