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

Purchase Instructions

PDF
포커스 모드
폰트 크기
마지막 업데이트 시간: 2024-10-30 10:06:01

Pay-as-You-go

Billing is based on usage duration. Account identity verification is required, and a 2-hour fee will be frozen at the time of purchase (vouchers cannot be used as a freezing deposit). The frozen resource fee will be returned upon termination. Before creating a cluster, users can check the available balance in the cloud billing account. If the balance is less than the amount that will be deducted by the system, recharge before making a purchase.
The cluster unit price is displayed hourly, but settlement is calculated based on the actual number of seconds used, rounded to two decimal places. The billing starts from the time the cluster is created and ends when the cluster termination operation is completed.
When you purchase a pay-as-you-go cluster, the fee for using the current configuration for 2 hours will be frozen in advance. Settlement occurs at every full hour (UTC+8), with fees deducted based on the actual usage duration of the cluster in the previous hour. When the configuration of a pay-as-you-go node is adjusted, the previously frozen fees will be unfrozen, and the fees will be re-frozen according to the latest configuration unit price, with a freeze period of 2 hours. When a pay-as-you-go cluster is terminated, the system will unfreeze the previously frozen fees.
If the account balance is insufficient and falls into arrears, see Arrears Explanation for more details.
See Vouchers for more details on Tencent Cloud voucher usage and restrictions.

Billing Example

Note
EMR on TKE cluster price inquiries only display EMR service fees, TencentDB for MySQL fees, and Cloud Block Storage (CBS) fees. It does not include TKE resource deployment fees or other associated cloud product fees.
Suppose you deploy an EMR on TKE cluster in Guangzhou Zone 7, with deployment services including Spark, Hive, and Impala. The Hive metadata storage is set to Cluster Default, and a TencentDB for MySQL is purchased as metadata storage. The cluster services do not enable external access, and the deployment information of cluster service roles is as follows:
Service
Deployment Type
Service Role
Data Volume Directory
POD Specification
Number of PODs
Spark
Default deployment
SparkJobHistoryServer
Host path
CPU: 8; memory: 16
2
Hive
Default deployment
HiveMetaStore
New PVC: Data disk: High-performance cloud disk 100G x 1
CPU: 4; memory: 8
1
HiveServer2
New PVC: Data disk: High-performance cloud disk 100G x 1
CPU: 4; memory: 8
1
Impala
Associated deployment
-
EMR product fee = Spark role deployment fee + Hive service deployment fee = 0.135432 + 0.067716 = 0.203148 USD/hour
Spark role deployment fee = SparkJobHistoryServer role deployment service fee x number of PODs x duration = (8 x 0.004617 + 16 x 0.00192375) x 2 x 1 = 0.135432 USD/hour
Hive role deployment fee = HiveMetaStore role deployment service fee x number of PODs x duration + HiveServer2 role deployment service fee x number of PODs x duration = (4 x 0.004617 + 8 x 0.00192375) x 1 x 1 + (4 x 0.004617 + 8 x 0.00192375) x 1 x 1 = 0.067716 USD/hour
Associated cloud product fee = TencentDB for MySQL metadata storage fee + Cloud disk deployment fee = 0.22 + 0.02 = 0.24 USD/hour MetaDB node fee (High IO Edition TencentDB, 4,000 MB of memory/100 GB of hard disk/1 instance) + disk size x unit price x number of service blocks x number of instances = 0.22 + 100 x 0.0001 x 1 x 2 = 0.24 USD/hour
Total fee displayed in price inquiry = EMR product fee + associated cloud product fee = 0.203148 + 0.24 = 0.443148 USD/hour
Impala deployment fee = No fees are incurred for associated deployment.
Note
The prices in this example are for reference only. See the actual purchase page for accurate fees, which do not include discount information.
For model specifications and pricing, see Product Pricing; for cloud disk pricing, see Cloud Disk Price Overview. For MetaDB pricing, see Cloud Database MySQL Billing Overview.
This example only involves associated products: Cloud Block Storage (CBS), TencentDB for MySQL, and POD resource fees.
The EMR bill only includes the POD deployment service fee. Bills for associated products can be viewed through their respective product pages. For EMR billing details, see Bill Inquiry or Tag Split Billing.

Purchase Method

Log in to the EMR Console, click Create Cluster on the EMR on CVM cluster list page, and complete the relevant configuration on the purchase page. For detailed instructions, see EMR on TKE Quick Start.


도움말 및 지원

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

피드백