- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- EMR on CVM Operation Guide
- Planning Cluster
- Configuring Cluster
- Managing Cluster
- Instance Information
- Node Specification Management
- Checking and Updating Public IP
- Logging in to Clusters
- Cluster Scale-Out
- Cluster Scale-in
- Releasing Now
- Auto Scaling
- Graceful Scale-In
- Changing Configurations
- Automatic Replacement
- Exporting Software Configuration
- Cluster Scripts
- Cluster Termination
- Operation Logs
- Task Center
- Disk Management
- Managing Service
- Monitoring and Alarms
- Cluster Overview
- Node Status
- Service Status
- Cluster Event
- Log
- Application Analysis
- Cluster Inspection
- Java Analysis
- Monitoring Metrics
- Node Monitoring Metrics
- HDFS Monitoring Metrics
- YARN Monitoring Metrics
- ZooKeeper Monitoring Metrics
- HBase Monitoring Metrics
- Hive Monitoring Metrics
- Spark Monitoring Metrics
- Presto Monitoring Metrics
- Trino Monitoring Metrics
- ClickHouse Monitoring Metrics
- Druid Monitoring Metrics
- Kudu Monitoring Metrics
- Alluxio Monitoring Metrics
- PrestoSQL Monitoring Metrics
- Impala Monitoring Metrics
- Ranger Monitoring Metrics
- COSRanger Monitoring Metrics
- Doris Monitoring Metrics
- Kylin Monitoring Metrics
- Zeppelin Monitoring Metrics
- Oozie Monitoring Metrics
- Storm Monitoring Metrics
- Livy Monitoring Metrics
- Kyuubi Monitoring Metrics
- StarRocks Monitoring Metrics
- Kafka Monitoring Metrics
- Alarm Configurations
- Alarm Records
- EMR on TKE Operation Guide
- EMR Lite HBase Operation Guide
- EMR Development Guide
- Hadoop Development Guide
- HDFS Common Operations
- HDFS Federation Management Development Guide
- HDFS Federation Management
- Submitting MapReduce Tasks
- Automatically Adding Task Nodes Without Assigning ApplicationMasters
- YARN Task Queue Management
- Practices on YARN Label Scheduling
- Hadoop Practical Tutorial
- Using API to Analyze Data in HDFS and COS
- Dumping YARN Job Logs to COS
- 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
- Hadoop Development Guide
- Practical Tutorial
- API Documentation
- FAQs
- Service Level Agreement
- Contact Us
- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- EMR on CVM Operation Guide
- Planning Cluster
- Configuring Cluster
- Managing Cluster
- Instance Information
- Node Specification Management
- Checking and Updating Public IP
- Logging in to Clusters
- Cluster Scale-Out
- Cluster Scale-in
- Releasing Now
- Auto Scaling
- Graceful Scale-In
- Changing Configurations
- Automatic Replacement
- Exporting Software Configuration
- Cluster Scripts
- Cluster Termination
- Operation Logs
- Task Center
- Disk Management
- Managing Service
- Monitoring and Alarms
- Cluster Overview
- Node Status
- Service Status
- Cluster Event
- Log
- Application Analysis
- Cluster Inspection
- Java Analysis
- Monitoring Metrics
- Node Monitoring Metrics
- HDFS Monitoring Metrics
- YARN Monitoring Metrics
- ZooKeeper Monitoring Metrics
- HBase Monitoring Metrics
- Hive Monitoring Metrics
- Spark Monitoring Metrics
- Presto Monitoring Metrics
- Trino Monitoring Metrics
- ClickHouse Monitoring Metrics
- Druid Monitoring Metrics
- Kudu Monitoring Metrics
- Alluxio Monitoring Metrics
- PrestoSQL Monitoring Metrics
- Impala Monitoring Metrics
- Ranger Monitoring Metrics
- COSRanger Monitoring Metrics
- Doris Monitoring Metrics
- Kylin Monitoring Metrics
- Zeppelin Monitoring Metrics
- Oozie Monitoring Metrics
- Storm Monitoring Metrics
- Livy Monitoring Metrics
- Kyuubi Monitoring Metrics
- StarRocks Monitoring Metrics
- Kafka Monitoring Metrics
- Alarm Configurations
- Alarm Records
- EMR on TKE Operation Guide
- EMR Lite HBase Operation Guide
- EMR Development Guide
- Hadoop Development Guide
- HDFS Common Operations
- HDFS Federation Management Development Guide
- HDFS Federation Management
- Submitting MapReduce Tasks
- Automatically Adding Task Nodes Without Assigning ApplicationMasters
- YARN Task Queue Management
- Practices on YARN Label Scheduling
- Hadoop Practical Tutorial
- Using API to Analyze Data in HDFS and COS
- Dumping YARN Job Logs to COS
- 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
- Hadoop Development Guide
- Practical Tutorial
- API Documentation
- FAQs
- Service Level Agreement
- Contact Us
Feature Introduction
EMR clusters support renewal to ensure that monthly subscription clusters do not become unavailable (isolated) due to fee-related issues. Renewal is at the resource level. This document introduces how to manually renew, set up automatic renewal, and cancel automatic renewal for monthly subscription nodes in the cluster through the EMR Console.
After automatic renewal is enabled, the system will automatically perform the renewal operation before the resource expires, eliminating the need for manual operation and ensuring you no longer have to worry about resource and data deletion due to delayed renewal.
If automatic renewal is not enabled, you can manually renew through the EMR console, with a minimum renewal period of one month.
Renewal Rules
1. The renewal feature only supports monthly subscription billing nodes. Pay-as-you-go nodes do not require renewal. Ensure that your account balance is sufficient for successful renewal.
2. The monthly subscription billing nodes to be renewed should be in a normal running status.
3. After automatic renewal is set up, the system will automatically renew monthly on the expiration date. Ensure that your account balance is sufficient to cover at least one month’s cost for prepaid resources.
4. If there are available vouchers during renewal, the system will automatically apply them. For more details, see Voucher.
5. If you manually renew before the deduction date, the system will automatically adjust the renewal to the latest expiration date.
Manual renewal
1. Log in to the EMR console and click the corresponding Cluster ID/Name in the cluster list to enter the cluster details page.
2. In the cluster details page, select Cluster resources > Resources, check the corresponding resources, and click Renew to select the resources that need renewal and proceed with the renewal operation.
3. By default, the renewal period is set to one month, but you can adjust the renewal duration as needed.
Automatic renewal
Setting Automatic Renewal in the EMR Console
When purchasing EMR clusters and scaling nodes out, you can enable automatic renewal for monthly subscription billing resources. If automatic renewal is not set for the monthly subscription billing resources during the cluster purchase or node expansion, you can follow the steps below to enable it later:
1. Log in to the EMR console and click the corresponding Cluster ID/Name in the cluster list to enter the cluster details page.
2. In the cluster details page, select Cluster Resources to enter the resource management page, where you can select individual nodes or multiple nodes to configure the settings.
When you configure automatic renewal for a single node, a Set Auto-Renew option will be added under More Operations in the operation column of the resource list.
When you configure automatic renewal for multiple nodes, the More Actions dropdown at the top supports the option to Set Auto-Renew.Node automatic renewal: Select Enable.
3. Disabling automatic renewal follows the same steps as described above.
Setting EMR Resource Automatic Renewal in Billing Center
1. Log in to the EMR console and click the corresponding Cluster ID/Name in the cluster list to enter the cluster details page.
2. In the cluster details page, select Cluster Resources to enter the resource management page, copy the corresponding resource ID, and then go to the Billing Center to set up automatic renewal.
3. In the Billing Center console, go to Renewal Management > Manual Renewal, find the resource you want to Set to Auto-Renewal, and change it to Automatic Renewal.
4. After refreshing the EMR console, you will see the renewal label on the corresponding resource ID in the Resources, indicating that automatic renewal has been set.
Yes
No
Was this page helpful?