Elastic MapReduce
- Release Notes and Announcements
- Announcements
- Security Announcements
- Product Introduction
- Product release
- Purchase Guide
- EMR on CVM Billing Instructions
- EMR on TKE Billing Instructions
- EMR Serverless HBase Billing Instructions
- Getting Started
- EMR on CVM Operation Guide
- Planning Cluster
- Cross-AZ Cluster
- Configuring Cluster
- Administrative rights
- Managing Cluster
- Auto Scaling
- Disk Management
- Managing Service
- Configuration Management
- YARN Resource Scheduling
- Monitoring and Alarms
- Application Analysis
- Monitoring Metrics
- EMR on TKE Operation Guide
- Configuring Cluster
- Permission Management
- Cluster Management
- Service Management
- Configuration Management
- Monitoring and Ops
- Application Analysis
- EMR Serverless HBase Operation Guide
- 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
- Basic Hive Operations
- Advanced Usage
- Presto Development Guide
- Sqoop Development Guide
- Hue 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
- Ranger User Guide
- Kafka Development Guide
- StarRocks Development Guide
- Flink Development Guide
- Practical Tutorial
- Practice of EMR on CVM Ops
- Data Migration
- Practical Tutorial on Custom Scaling
- Practical Tutorial on Setting Scaling Rules
- API Documentation
- Making API Requests
- Cluster Resource Management APIs
- Cluster Services APIs
- FAQs
- EMR on CVM
Purchase Instructions
Last updated: 2025-01-24 09:24:25
Monthly Subscription
Fees are paid for one month, multiple months, or even years in advance, and real-name authentication is required for the account. This mode applies to long-term clusters with stable needs for compute resources. The fees are charged by calendar month and are lower compared with the pay-as-you-go mode.
Calendar month:
Cycle for February 2016: 00:00:00 February 1 - 23:59:59 February 29.
Cycle for May 2017: 00:00:00 May 1 - 23:59:59 May 31.
Before you create a cluster, you can check the available balance of your account. If the balance is insufficient for deduction, top up first before purchase.
For payment overdue caused by insufficient account balance, see Payment Overdue.
For instance termination and refund in monthly subscription mode, see Refund Instructions.
For renewal in monthly subscription mode, see Cluster Renewal.
For the use and restrictions of Tencent Cloud vouchers, see Promo Vouchers.
If your account balance is sufficient and have enabled automatic renewal, the fees for the next billing cycle (including fees for nodes and other involved cloud products) will be automatically deducted on the expiration date, and the next cycle will start automatically.
Pay-As-You-Go
You are charged by usage duration of a cluster. This billing mode requires identity verification and will freeze an amount of 2-hour usage fee when the cluster is purchased (vouchers cannot be used here). After this cluster is terminated, the frozen amount will be refunded. Before creating a cluster, check your Tencent Cloud account balance. If your balance is less than the service cost, top up your account first.
When you purchase an EMR cluster, the price will be listed as an hourly fee. However, you will be billed by the actual seconds of usage and the charge will be rounded to two decimal places. Billing starts from the second the cluster is created and stops the second the cluster is terminated.
When you purchase a pay-as-you-go cluster, the fee for 2-hour usage under the current configuration will be frozen in your account balance as a deposit. You will then be billed by the hour for your usage over the past hour. When you change the node configuration, the frozen amount will be unfrozen and a new 2-hour deposit will be frozen based on the unit price of the new configuration. Your deposit will be released back to your account when the cluster is terminated.
For information about what you can do when your account balance is insufficient, see Payment Overdue.
For information about the use and limits of Tencent Cloud vouchers, see Promo Vouchers.
Spot Instance
Similar to pay-as-you-go instances, spot instances are charged by second and billed by hour. The prices of spot instances fluctuate according to market demand, which provide you with a substantial discount (about 80-90% off the prices of pay-as-you-go instances with the same specifications). However, spot instances may be repossessed automatically by the system as a result of inventory shortages or higher bids from other users.
For more information about spot instance policies, use cases, and limitations, see Spot Instance.
Note:
Spot instances only support auto scaling to replace compute nodes. The system may repossess spot instances due to higher bids from other users. Therefore, please use them with caution.
Billing Example
Monthly Subscription
Suppose you have created a Hadoop cluster in Guangzhou Zone 7. It is a high-availability cluster of the EMR-V3.5.0 version, with the application scenario of "default scenario". The deployed services include hdfs-3.2.2, yarn-3.2.2, zookeeper-3.6.3, openLDAP-2.4.44, knox-1.6.1, and hive-3.1.3 (default storage method selected for the Hive metadata). The purchase duration is 1 month, and the applied discount is 15% off for EMR, 5% off for CBS, and 10% off for TencentDB for MySQL (CDB).
Note：
The above discounts are for reference only. The specific discounts are subject to the actual situation.
EMR cluster fees are as follows:
Node Type | Model and Specification | System Disk | Data Disk | Model and Specification Fees | System Disk Fees | Data Disk Fees | Number of Nodes |
master | Standard SA2: 4 cores and 16 GB | Cloud SSD 50 GB × 1 | Cloud SSD 200 GB × 1 | 397.44 | 1 × 50 GB × 1 | 1 × 200 GB × 1 | 2 |
core | Standard SA2: 4 cores and 8 GB | Cloud SSD 50 GB × 1 | Cloud SSD 200 GB × 1 | 264.96 | 1 × 50 GB × 1 | 1 × 200 GB × 1 | 3 |
common | Standard SA2: 2 cores and 4 GB | Cloud SSD 50 GB × 1 | Cloud SSD 200 GB × 1 | 132.48 | 1 × 50 GB × 1 | 1 × 200 GB × 1 | 3 |
MetaDB | High I/O TencentDB 4,000 MB of memory / 100 GB of hard disk size / 1 node | | | | | USD 480/node | 1 |
Master node fees = ((model and specifications fees + system disk fees) × discount + data disk fees × discount) × the number of nodes = ((397.44 + 50) × 0.85 + 200 × 1 × 0.95) × 2 = 1,140.648 (USD/month)
Core node fees = ((model and specifications fees + system disk fees) × discount + data disk fees × discount) × the number of nodes = ((264.96 + 50) × 0.85 + 200 × 1 × 0.95) × 3 = 1,373.148 (USD/month)
Common node fees = ((model and specifications fees + system disk fees) × discount + data disk fees × discount) × the number of nodes = ((132.48 + 50) × 0.85 + 200 × 1 × 0.95) × 3 = 1,035.324 (USD/month)
MetaDB node fees = MetaDB list price × discount = 480 × 0.9 = 432 (USD/month)
Total fees = master node fees + core node fees + common node fees + MetaDB node fees = 1,140.648 + 1,373.148 + 1,035.324 + 432 = 3,981.12 (USD/month)
Note：
The fees in this example are for reference only. For the actual fees, see the purchase page.
For model and specifications pricing, see Billing Overview. For cloud disk pricing, see the Price Overview of cloud disk. For MetaDB pricing, see the Billing Overview of TencentDB for MySQL.
The above example only involves CBS and CDB.
EMR bills involve only CPU, memory, system disk, and local data disk.For bills of other involved products, go to the Tencent Cloud console.. For EMR bills, see Viewing Bills or Cost Allocation by Tag.
Master and common nodes do not support deployment with local disks.
Pay-as-you-go
Suppose you have created a Hadoop cluster in Guangzhou Zone 7. It is a high availability cluster of the EMR-V3.5.0 version, with the application scenario of "default scenario". The deployed services include hdfs-3.2.2, yarn-3.2.2, zookeeper-3.6.3, openLDAP-2.4.44, knox-1.6.1, and hive-3.1.3 (default storage method selected for the Hive metadata). The billing mode is pay-as-you-go, and the applied discount is 15% off for EMR, 5% off for CBS, and 10% off for TencentDB for MySQL (CDB).
Note:
The above discounts are for reference only. The specific discounts subject to the actual situation.
EMR cluster fees are shown below:
Node Type | Model Specification | System Disk | Data Disk | Model Specification Fee | System Disk Fee | Data Disk Fee | Number of Nodes |
Master | Standard SA2: 4-core CPU, 16 GB memory | SSD 50 GB × 1 | SSD 200 GB × 1 | 0.77 | 0.0025 × 50 GB × 1 | 0.0025 × 200 GB × 1 | 2 |
Core | Standard SA2: 4-core CPU, 8 GB memory | SSD 50 GB × 1 | SSD 200 GB × 1 | 0.52 | 0.0025 × 50 GB × 1 | 0.0025 × 200 GB × 1 | 3 |
Common | Standard SA2: 2-core CPU, 4 GB memory | SSD 50 GB × 1 | SSD 200 GB × 1 | 0.26 | 0.0025 × 50 GB × 1 | 0.0025 × 200 GB × 1 | 3 |
MetaDB | High I/O TencentDB 4,000 MB of memory / 100 GB of disk size / 1 node | | | | | USD 1.28/node | 1 |
Master node fee = ((0.77 + 0.125) × 0.85 + 200 × 0.0025 × 0.95) × 2 = 2.4715 (USD/hour)
Core node fee = ((0.52 + 0.125) × 0.85 + 200 × 0.0025 × 0.95) × 3 = 3.06975 (USD/hour)
Common node fee = ((0.26 + 0.125) × 0.85 + 200 × 0.0025 × 0.95) × 3 = 2.40675 (USD/hour)
MetaDB node fee = 1.28 × 0.9 = 1.152 (USD/hour)
Total fee = 2.4715 + 3.06975 + 2.40675 + 1.152 = 9.1 (USD/hour)
Note:
The prices provided in this example are for reference only. Refer to the purchase page for actual fees.
For information about model specifications and pricing, see Pricing | Elastic MapReduce.
The above example only involves the following associated products: CBS and CDB.
EMR bills only show the costs of nodes, namely, the costs of CPU, memory, system disk, and local data disk. The bills of associated cloud products are available in their respective consoles. For EMR bill details, see Viewing Bills or Cost Allocation by Tag.
Purchase
Evaluating your business
Before purchasing a cluster, you need to evaluate your business according to the actual situation to ensure that the created cluster meets your actual needs. For more information, see Business Evaluation.
Purchasing EMR clusters
Before using EMR services, you need to register a Tencent Cloud account and go to the EMR purchase page to purchase an EMR cluster. For more information, see Creating Cluster.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No