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

Cluster Renewal

PDF
フォーカスモード
フォントサイズ
最終更新日: 2025-07-03 11:34:54

Feature Introduction

Elastic MapReduce (EMR) clusters support the renewal feature, which ensures that monthly subscribed clusters do not become unavailable (isolated) due to payment issues. This document describes how to manually renew, enable auto-renewal, and cancel auto-renewal for monthly subscribed cluster nodes through the EMR console.
After auto-renewal is enabled, the system will automatically renew resources before they expire. No manual action is required, and you do not have to worry about resources and data being deleted due to untimely renewal.
If the auto-renewal feature is not enabled, you can manually renew through the EMR console. Manual renewal supports a minimum renewal period of 1 month.

Renewal Rules

1. The renewal feature only supports monthly subscribed nodes. Pay-as-you-go nodes do not require renewal operations. Ensure your account balance is sufficient to guarantee normal renewals.
2. The monthly subscribed nodes to be renewed must be in normal operation status.
3. After you enable auto-renewal, resources will be renewed automatically every month on the expiration day. You need to ensure that your account balance is sufficient to prepay the fees for at least 1 month.
4. If there are available vouchers at the time of renewal, the system will automatically use them. For details, refer to the Voucher documentation.
5. If you manually renew before the deduction time, the system will automatically renew based on the latest expiration time.

Manual Renewal

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. On the cluster details page, select Cluster Resources > Resources, select the corresponding resources, and click Renew or Pending Renewal to filter out the resources that need renewal to proceed with the renewal operation.
3. The default renewal duration is 1 month, which can be adjusted as needed.

Auto-renewal

Setting Auto-renewal in the EMR Console

When purchasing clusters and scaling out nodes in the EMR console, you can enable auto-renewal for monthly subscribed resources. If auto-renewal was not enabled for monthly subscribed resources during cluster purchase or node scale-out, you can follow these steps to set up auto-renewal later:
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. On the cluster details page, select Cluster Resources to enter the Resources page. You can select nodes individually or in batches for settings.
When setting auto-renewal for a single node, an additional Set renewal option will appear in the More drop-down list of the operation column of the resource list.
When setting auto-renewal for nodes in batches, you can select Set renewal from the More drop-down list at the top.
Node auto-renewal: Select Enable.
3. To disable auto-renewal, follow the same operations as above.

Setting Auto-renewal for EMR Resources in the Billing Center

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. On the cluster details page, select Cluster Resources to enter the Resources page, copy the corresponding resource ID, and go to Billing Center to set up auto-renewal.
3. In the Renewal Management > Manual Renewal section of the Billing Center console, find the resource that needs auto-renewal and set it to Auto-renewal.
4. After refreshing the EMR Console, you will see the word "Renew" next to the corresponding resource ID in Resources, indicating that auto-renewal has been enabled.

ヘルプとサポート

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

フィードバック