Esta página ainda não está disponível no idioma selecionado. Estamos trabalhando para adicionar mais opções de idiomas. Agradecemos sua compreensão.
- Service Overview
- Billing
- Getting Started
-
User Guide
-
HBase User Guide
-
HBase Cluster Management
- Overview
- Managing Clusters
- Preparing an ECS
- Using HBase
- HBase Cold and Hot Data Separation
- HBase Thrift Server
- HBase Security Channel Encryption
- HBase Batch Data Import
- HBase Monitoring Clusters
- Self-Healing from HBase Hotspotting
- Global Secondary Indexes
-
HBase Cluster Management
-
ClickHouse User Guide
-
ClickHouse Cluster Management
- Overview
- Managing ClickHouse Clusters
- Using ClickHouse
- Migrating ClickHouse Data
- ClickHouse User Management
- ClickHouse Role Management
- ClickHouse Slow Query Management
- Configuring Secure Channel Encryption for ClickHouse Clusters
- Application of ClickHouse Cold and Hot Data Separation
- ClickHouse Monitoring Clusters
-
ClickHouse Cluster Management
- Permissions Management
- Audit Logs
- Cluster Log Management
-
HBase User Guide
-
Developer Guide
- HBase Application Development Guide
- ClickHouse Application Development Guide
-
FAQs
-
General
- What Services Does a CloudTable Cluster Provide?
- Why Do I Choose CloudTable Service?
- How Do I Prepare for Creating a CloudTable HBase Cluster?
- What Should I Pay Attention to When Using CloudTable Service?
- What Compression Algorithms Are Supported by CloudTable HBase Clusters?
- Can I Stop CloudTable Service?
- Which Programming Languages Are Supported by HBase External APIs in CloudTable?
- How Do I Determine the Number of Faulty RegionServers?
- What Special Characters Does CloudTable HBase Support?
- What Can I Do If the Index Table Does Not Match the Data Table After CloudTable Data Is Deleted?
- What Should I Do If Concurrent Tasks Run Slowly When Python Accesses CloudTable Through Thrift?
- How do I view the TTL attribute of HBase shell?
- Why Are My Server Resources Released?
- How Do I Delete a Cluster?
- How Do I Stop Services and Release Resources?
-
Connection and Access
- How Do I Access a CloudTable Cluster?
- Can I Use SSH to Access Computing Nodes of CloudTable?
- Why Can't I Access HBase After the ZK Address Is Configured?
- Why Is the Error "Will not attempt to authenticate using SASL (unknown error)" Reported When Connecting to HBase?
- How Do I View the IP Address Corresponding to a Domain Name in a CloudTable Link?
- How Do I Access CloudTable from Other Cloud Services?
- Can I Configure the hbase-site.xml File?
- How Do I Query the Creation Time of a Table in CloudTable HBase?
-
Data Read/Write
- Is Raw Data Stored in CloudTable HBase?
- Why Can't I Write Data to HBase?
- What Is the Maximum Size of Data Written to the HBase Cluster?
- How Do I Check the Daily Incremental Data in HBase Tables?
- What Should I Do If an Error Is Reported When I Access the CloudTable HBase Cluster?
- How Do I Delete the Backup Table of the ZooKeeper Node in the ClickHouse Cluster?
- What Should I Do If a Database Missing Error Occurs When a Table Is Created in the ClickHouse Cluster?
- Billing FAQs
-
General
- General Reference
Copied.
Yearly/Monthly Billing
Yearly/Monthly billing is a prepaid billing mode in which you pay before using resources. It is suitable when your resource requirements are fixed because you can pay less by using longer. This section describes the billing rules for yearly/monthly CloudTable resources.
Application Scenario
In yearly/monthly billing mode, you need to pay for a required duration in advance. This mode is suitable for long-term and relatively fixed service requirements. The yearly/monthly billing mode is recommended for the following scenarios:
- Long-term workloads with stable resource requirements, such as official websites, online malls, and blogs.
- Long-term projects, such as scientific research projects and large-scale events.
- Workloads with predictable traffic bursts, for example, e-commerce promotions or festivals.
Billed Items
You are billed for the following items on a yearly/monthly basis.
Item |
Description |
---|---|
Compute |
Compute specifications of a node |
Storage |
Storage specifications and capacity of a node |
Nodes |
Number of nodes |
If you want to purchase a(n) HBase/ClickHouse cluster, the price will be displayed at the bottom of the page, as shown in the following figure.


You are charged for:
- Node quantity
- Storage specifications
Billing Usage Period
A yearly/monthly CloudTable instance is billed for the purchased duration. The billing starts when you activated or renewed the subscription, and ends at 23:59:59 of the expiry date.
For example, if you purchased a one-month CloudTable instance on March 08, 2023, 15:50:04, the billed usage period is from March 08, 2023, 15:50:04 to April 08, 2023, 23:59:59.
Billing Examples
Suppose you purchased an instance on March 8, 2023, 15:50:04. The charged resources include compute units and data storage. Assume the subscription is for one month, and will be manually renewed for one month before it expires:
- The first billing period: Mar 08, 2023, 15:50:04–Apr 08, 2023, 23:59:59
- The second billing period: Apr 08, 2023, 23:59:59–May 08, 2023, 23:59:59
You must prepay for each billing period. Table 2 shows the billing formula.
Item |
Formula |
Unit Price |
---|---|---|
Compute |
Unit price of node specifications x Required duration x Number of nodes |
The actual fee depends on the price displayed on the console. |
Storage |
Data storage unit price x Data storage capacity x Number of nodes x Required duration |
The actual fee depends on the price displayed on the console. |
The prices in the figure are just examples. The actual prices are those displayed on the Billing Center.


Impact on Billing After Specification Change
If the specifications of a yearly/monthly CloudTable instance no longer meet your needs, you can change the specifications on the console. The system will recalculate the price and either bill or refund you the difference.
- HBase configuration change: horizontal scale-out.
- ClickHouse configuration change: horizontal scale-out, disk capacity expansion, and specification change.
Impacts of Expiration
Figure 5 shows the statuses a yearly/monthly CloudTable resource can go through throughout its lifecycle. After an instance is purchased, it enters the valid period and runs normally during this period. If the instance is not renewed after it expires, before being deleted, it first enters a grace period and then a retention period.
Expiration Reminder
From the 7th day before a yearly/monthly CloudTable instance expires, the system will send an expiration reminder to the creator of the Huawei Cloud account by email, SMS, and internal message.
Impact After Expiration
If your yearly/monthly CloudTable instance is not renewed after it expires, it changes to the Expired state and enters a grace period. During this period, you can still access CloudTable.
If the yearly/monthly CloudTable instance is not renewed after the grace period ends, its status turns to Frozen and it enters a retention period. You cannot perform any operations on the resource while it is in the retention period.
If the yearly/monthly CloudTable instance is not renewed by the time the retention period ends, the compute resources (vCPUs and memory), EVS disks, and EIPs will be released and data cannot be restored.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot