El contenido no se encuentra disponible en el idioma seleccionado. Estamos trabajando continuamente para agregar más idiomas. Gracias por su apoyo.
- 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
Show all
Copied.
HBase Billing Examples
Billing Scenario
A user purchased a pay-per-use HBase cluster on March 18, 2023, 15:00:00 and used the cluster for one hour. After 0.5 hour, the user added Core nodes for the cluster (from three nodes to six nodes). The user changed the cluster to yearly/monthly on March 18, 2023, 15:59:59 for a long-term use. The validity period was one month, and the cluster expired at 23:59:59 on April 18, 2023. This section shows how to count the total fee for using this cluster. Suppose the cluster specifications are as follows:
- Master node specifications
- Compute: 4U16G
- Storage: Ultra-high I/O and 200 GB/Node
- Nodes: 3 (The cluster is configured with HA by default, which needs Master nodes. One Master node is provided for free for cluster monitoring.)
- Core node specifications
- Compute: 4U16G
- Storage: High I/O and 400 GB/Node
- Nodes: 3
Billing Analysis
|
Billing Mode |
Formula |
Billing Cycle |
Price |
|---|---|---|---|
|
Pay-per-use billing (before node addition) |
Compute unit fee: Unit price of a compute unit x Number of nodes |
Hourly fee |
Master nodes: 0.2992 (Unit price of a compute unit: USD/hour) x 2 (Node quantity) x 1 (Usage duration: hour) = $0.5984 USD Core nodes: 0.2992 (Unit price of a compute unit: USD/hour) x 3 (Node quantity) x 1 (Usage duration: hour) = $0.8976 USD |
|
Disk fee: Disk unit price x Capacity x Number of nodes |
Core nodes: 0.00008 (Unit price of a disk: USD/hour) x 400 (Disk capacity: GB) x 3 (Node quantity) x 0.5 (Usage duration: hour) = $0.048 USD |
||
|
Total Price: $1.544 USD |
|||
|
Pay-per-use billing (after node addition) |
Compute unit fee: Unit price of a compute unit x Number of nodes |
Hourly fee |
Master nodes: 0.2992 (Unit price of a compute unit: USD/hour) x 2 (Node quantity) x 1 (Usage duration: hour) = $0.5984 USD Core nodes: 0.2992 (Unit price of a compute unit: USD/hour) x 6 (Node quantity) x 1 (Usage duration: hour) = $1.7952 USD |
|
Disk fee: Disk unit price x Capacity x Number of nodes |
Core nodes: 0.00008 (Unit price of a disk: USD/hour) x 400 (Disk capacity: GB) x 6 (Node quantity) x 1 (Usage duration: hour) = $0.192 USD |
||
|
Total price: $2.5856 USD |
|||
|
Yearly/Monthly billing |
Compute unit fee: Unit price of a compute unit x Number of nodes |
Monthly fee |
Master nodes: $136.92 (Unit price of a compute unit: USD/month) x 2 (Node quantity) = $273.84 USD Core nodes: $136.92 (Unit price of a compute unit: USD/month) x 6 (Node quantity) = $821.52 USD |
|
Disk fee: Disk unit price x Capacity x Number of nodes |
Core nodes: 0.05 (Unit price of a disk: USD/month) x 400 (Disk capacity: GB) x 6 (Node quantity) = $120 USD |
||
|
Total |
Total Price: $1215.36 USD |
From March to April, the total fee of the HBase cluster is $1217.9456 USD (2.5856 + 1215.36).
NOTE:
- HBase clusters are charged by hour. The smallest billing unit for compute unit usage is one hour, and partial hours are counted as full hours.
- Periodic Settlement of Pay-per-Use Products:
- Settlement by hour: Huawei Cloud calculates the fee based on your usage every hour and deducts the fee from your account. For example, fees incurred from 8:00 to 9:00 are usually deducted before 10:00.
- Settlement by month: Huawei Cloud calculates the fee based on your usage and deducts the fee of the month at the beginning of the next month. For example, fees incurred from 00:00:00 on April 1, 2019 to 23:59:59 on April 30, 2019 are usually deducted at about 01:00:00 on May 1, 2019.
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
