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

Payment Overdue

PDF
フォーカスモード
フォントサイズ
最終更新日: 2026-03-20 17:40:32
Note: If you are a customer of a Tencent Cloud partner, the rules regarding resources when there are overdue payments are subject to the agreement between you and the partner.

Monthly Subscription Cluster

Alerts

You will receive the following alerts after specifying the recipients and receiving channels in Message Subscription Management.
Type
Description
Expiration Alert
Expiration alerts will be sent within 7 days before the cluster resources get expired. The alerts will notify the Tencent Cloud account creator, global resource collaborator, and financial collaborator via email and SMS messages.
Overdue Payment Alert
Overdue payment alerts will be sent on and after the expiration date of cluster resources. The alerts will notify the Tencent Cloud account creator and all collaborators via email and SMS messages.

Automatic Renewal Enabled

The system starts sending renewal reminders 7 days before the expiration of cluster, and checks every day to see whether the account balance is sufficient for the cluster resources with automatic renewal enabled.
If the account balance is sufficient, the system will automatically renew for the cluster resources on their expiration date.
If the account balance is insufficient, the system will send a notification to the Tencent Cloud account creator and all collaborators, informing them of the insufficient balance and advising them to recharge.
If some resources have expired and the account balance is insufficient, the system will prioritize renewing the cluster resources that will expire sooner, and handle the other cluster resources as expired resources. The user will be notified that automatic renewal failed due to insufficient available account balance, and some cluster resources have expired.
Note:
7 days before the expiration, the check starts. If insufficient account balance is detected, notifications will be sent starting from the day when the balance becomes insufficient. Since the first notification day to the day when the EMR cluster resources get expired, notifications will be sent every other day.

Automatic Renewal Disabled

The system will send expiration alerts to users within 7 days before the expiration date of the EMR cluster resources, one notification every other day. Each cluster will receive 3-4 alerts to notify users to renew the resources in time. If renewal is not completed until the expiration date, the user will be notified that the resources have expired.

Repossession Mechanism

If the cluster expires (including the expiration date) and renewal is not completed, the system will suspend cluster services 7 days after the expiration. The cluster and nodes (CVM) will enter the recycle bin. After entering the recycle bin, the cluster and nodes will be inaccessible, and only the data will be retained. The isolation period lasts 7 days. In addition, the resources in the recycle bin will not proactively unbind from Cloud Load Balancer (CLB), elastic cloud disks, or basic networks; therefore, the unrenewed resources will not incur fees, but network fees incurred during this period and data storage (CBS) will still be charged.
During the isolation period, the cluster can be renewed to restore access. The start time for the renewal cycle of the restored instance will be the expiration time of the previous cycle.
If your EMR cluster is not renewed within 7 days (including the 7th day) after service suspension, the system will release the resources about 24 hours after the 7-day suspension period. Once released, EMR cluster data will be erased and cannot be restored.
Traditional account type: The EIP bound to the instance will be released simultaneously.
Standard account type: The EIP bound to the instance will be retained. If this EIP is no longer used, release it in time.
For how to distinguish traditional account type and standard account type, see Checking Account Type.
Note
Suspend service: Indicates that the resources have stopped providing services. Users can no longer use the services. However, the data is not cleared yet, and users can resume the resources.
Release: Indicates that the resource data has been deleted and cannot be restored.

Pay-As-You-Go

Overdue payment alerts

Type
Description
Overdue payment reminder
Pay-as-you-go clusters are billed on the hour. When your account balance becomes negative, your Tencent Cloud account creator, global resource collaborators, and financial collaborators will be notified by email and SMS.
Balance alert
This feature is disabled by default. To enable it, see "Balance Notifications".

Overdue policy

When your account balance falls below zero, a pay-as-you-go cluster can be used for 2 more hours, and the usage will still be deducted from your account. After 2 hours, the cluster will be moved to the recycle bin and become unavailable, and will no longer incur pay-as-you-go costs.
Time After Service Suspension
Description
≤ 15 days
If your account is topped up to a positive balance, the charging will continue, and the cluster will be automatically recovered.
If your account balance remains negative, the cluster cannot be recovered.
> 15 days
If your account is not topped up to a positive balance, your pay-as-you-go cluster resources will be repossessed and released. All data will be cleared and cannot be recovered. When your cluster resources are repossessed, your Tencent Cloud account creator and all collaborators will be notified by email and SMS.
Note:
If a pay-as-you-go cluster is no longer needed, terminate it as soon as possible to avoid incurring further costs.
After a cluster is terminated, the data in it will be cleared and cannot be recovered.
Because your resource usage changes constantly, the balance alerts may not be precisely accurate.
You will continue to be charged for associated cloud products such as EIP and CBS during cluster isolation due to overdue payments until your account balance becomes negative.

Overdue Payments of Associated Cloud Products

Product
Description
EIP
Elastic IP Payment Overdue
TencentDB for MySQL (CDB)
CBS
COS
CHDFS
VPC


ヘルプとサポート

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

フィードバック