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

Overdue Payment

PDF
포커스 모드
폰트 크기
마지막 업데이트 시간: 2024-11-28 16:22:15

Monthly Subscription Instances

You will receive the alert below after you specify the recipients and receiving channels on the message subscription page.

Alerts

Type
Description
Expiration Alert
An expiration alert will be sent seven, five, three, and one day before cloud resource expiration, as well as on the expiration day. The Tencent Cloud account creator, global resource collaborator, and financial collaborator will receive such notifications via email and SMS message.
Overdue Payment Alert
An overdue payment alert will be sent on the cloud resource expiration day and after the expiration. The Tencent Cloud account creator and all collaborators will receive such notifications via email and SMS.

Repossession Mechanism

The system starts sending renewal reminders seven days before the expiration of cloud service resources.
If your account balance is sufficient and automatic renewal is enabled, the resources will be automatically renewed on the expiration date.
If your instances are not renewed before expiration (or on the expiration date), the system will suspend the services within approximately 48 hours after expiration. (Instances are isolated but not shut down, with data retained.) The instances will be moved to the recycle bin.
Instances not renewed upon expiration will not incur fees, but network fees will still be charged.
You can renew and restore instances within seven days after the services are suspended.
Note:
The renewal cycle start date for renewed instances is the expiration date of the previous cycle.
If your instances are not renewed within seven days (included) after services are suspended, the system will release the resources within approximately 24 hours seven days after the service suspension. The data of expired instances will be deleted, which cannot be restored.

Pay-As-You-Go Pricing Instance

Overdue Payment Reminder

Type
Note
Overdue Payment Reminder
The system bills pay-as-you-go resources on the hour. When your account balance becomes negative, the Tencent Cloud account creator, global resource collaborators, and financial collaborators will be notified via email and SMS.
Arrears Reminder
This feature is disabled by default. To enable this feature, see Balance Notifications.

Overdue Payment Handling

When the account balance becomes negative, pay-as-you-go instances can continue to be used and billed for the next two hours. After two hours, pay-as-you-go instances will stop being billed and automatically enter the Recycle Bin due to Automatic Service Suspension.
Time After Automatic Service Suspension
Note
≤ 15 days
1. If your account is topped up to a positive balance, billing will resume, and the instances will automatically recover.
2. If your account balance is not topped up to a positive value, the instances cannot be recovered.
> 15 days
If your account is not topped up to a positive balance, the pay-as-you-go instance resources will be repossessed and released, all data will be cleared and cannot be recovered. When the instance resources are repossessed, we will notify the Tencent Cloud account creator and all collaborators via Email and SMS.
Note:
When you no longer need to use pay-as-you-go instances, terminate them promptly to avoid continued fee deductions.
After an instance is terminated, its data will be cleared and cannot be recovered.
Since your actual resource consumption changes constantly, some slight discrepancies may exist for the stated balance in the low balance alert.
The network fees and other associated products will continue to be charged normally during the debt isolation period until the account balance becomes negative.


도움말 및 지원

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

피드백