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

Mount Cloud Disks

PDF
Mode fokus
Ukuran font
Terakhir diperbarui: 2026-03-20 16:00:04

Feature Introduction

As your business grows, scenarios such as insufficient data storage space on nodes in the cluster and insufficient random IOPS and throughput I/O capabilities of disks may occur. In such scenarios, you need to add new cloud disks. This document describes how to mount cloud disks to nodes in the Elastic MapReduce (EMR) console.
Note:
1. A single node can mount up to 20 cloud disks.
2. Only cloud data disks support additional mounting of cloud disks, while system disks do not.
3. Pods, recycle bin resources, and mateDB do not support additional mounting of cloud disks.
4. After a disk is mounted successfully, users need to create EMR-related files and paths by themselves, and configure and restart the service at an appropriate time for the business.
5. When mounting the multi-node cloud disks in batches, you can perform operations in batches for nodes with the same billing mode, availability zone, node type, or node specifications.

Directions

The EMR console supports 2 ways of additionally mounting cloud disks: Newly Purchased Cloud Disk and Existing Cloud Disk. After the disks are mounted on the nodes in the above 2 ways, the system will complete the disk initialization.
Newly Purchased Cloud Disk: Supports single-node and multi-node batch mounting. When batch mounting the multi-node cloud disks, you can perform operations in batches for nodes with the same type, size, or number of blocks. The billing type of a newly purchased cloud disk is consistent with the billing mode of the node to be mounted, and the lifecycle of a newly purchased cloud disk is released along with the node.
Existing Cloud Disk: Only batch mounting of existing cloud disks (with the same billing type as the node) on a single node is supported, and the release principle is to be released along with the node.

New Purchased Cloud Disk (Recommended)

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 Disk Mounting: Select the node to be mounted and select More > Disk Adjustment > Mount Cloud Disk in the Operation column of the list to enter the cloud disk mounting configuration page.
2.2 Multi-Node Cloud Disk Batch Mounting: Select Disk Adjustment > Mount Cloud Disk under the More Operations header and enter the cloud disk mounting configuration page.
3. On the configuration page, select New Purchased Cloud Disk as the origin of cloud disk, and choose the disk type, disk size, and the number of disks mounted on a single node as needed.
4. Configure the service directory as needed. The newly mounted disk will be written into the selected service directory, and the configurations will be distributed. After the disk is successfully mounted, you need to restart the service manually for the configurations to take effect.

Existing Cloud Disk

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 Disk Mounting: Select the node to be mounted and select More > Disk Adjustment > Mount Cloud Disk in the Operation column of the list to enter the cloud disk mounting configuration page.
2.2 Multi-Node Cloud Disk Batch Mounting: Select Disk Adjustment > Mount Cloud Disk under the More Operations header and enter the cloud disk mounting configuration page.
3. On the configuration page, select Existing Cloud Disk as the origin of cloud disk. You can choose a cloud disk whose status is To be mounted in the availability zone of the current node.
4. (Pay-as-you-go node) Release Action: Release with instance is checked by default.
5. (Monthly subscription node) When the expiration time of the mounted single disk is inconsistent with and is shorter than that of the node, there are two options:
5.1 Align with the expiration time of the node (instance). The disk's expiration time will be extended to the node's expiration time.
5.2 Auto-renew the disk monthly upon expiration (recommended).
6. Configure the service directory as needed. The newly mounted disk will be written into the selected service directory, and the configurations will be distributed. After the disk is successfully mounted, you need to restart the service manually for the configurations to take effect.

Bantuan dan Dukungan

Apakah halaman ini membantu?

masukan