Release Notes
Announcements
Security Announcements
Billing Mode | Monthly Subscription | Pay-As-You-Go | Spot Instance |
Payment method | |||
Billing unit | USD/month | USD/second | USD/second |
Unit price | Relatively lower | Relatively higher | The price fluctuates. In most cases, the price is about 10-20% of the price of a pay-as-you-go instance with the same specifications. |
Minimum use time | At least one month (calendar month) | Charged by second and billed by hour. Purchase and release at any time. | Charged by second and billed by hour. Purchase and release at any time. May be repossessed by the system. |
Configuration change | Upgrade configuration at any time. No limit for each node (CPU and memory only). | No limit. Change (node CPU and memory only) at any time. | Not supported |
Use case | Suitable for long-term clusters with stable needs for compute resources. | Suitable for a cluster to exist for a short period or periodically. | Suitable for a cluster using elastic compute resources to get more computing power. |
Billing mode change | Not supported | Not supported | Not supported |
Cost Category | Billable Item | Resource Use in EMR | Billing Description | Pricing |
Costs of EMR nodes | Node cost | You can select the model specifications as needed. The nodes are subject to separate pricing by EMR. The price of a node covers its resources such as CPU, memory, system disk, and local data disk. Three billing modes are available: pay-as-you-go ,monthly subscription and spot instance. | The EMR cost is only the costs of all nodes. | |
Costs of associated cloud products | Elastic IP (EIP) | Public network access is enabled for the Master.1 node in a cluster by default so that you can access the WebUI pages of various Hadoop components from outside the cluster. Traffic fees are incurred for data interactions when you visit these pages, but a little traffic is generated in most cases. Therefore, the bill-by-traffic mode is used by default, which costs less than the bill-by-bandwidth mode. | ||
| TencentDB for MySQL (CDB) | If you plan to deploy one or more components among Hive (local), Hue, Ranger, Oozie, Druid, and Superset in an EMR cluster, you need to purchase a CDB instance for storing metadata. | ||
| Cloud Block Storage (CBS) | If you plan to deploy cloud disks as the data disks in a node, you need to purchase at least one cloud disk. The cost of the cloud disk will be paid together with the EMR node purchased, with the corresponding CBS order generated. The cloud disk will be subject to the same billing mode as the node. | ||
| Cloud Object Storage (COS) | If you use COS to separate the compute and storage resources of a cluster, you will be charged for data storage and requests when the cluster requests to pull data stored in COS for computing. Meanwhile, result data storage, backup, or other operations in the computing will also generate new data in COS. | ||
| Cloud HDFS (CHDFS) | If you use CHDFS to separate the compute and storage resources of a cluster, you will be charged for data storage and requests when the cluster requests to pull data stored in CHDFS for computing. Meanwhile, result data storage, backup, or other operations in the computing will also generate new data in CHDFS. | ||
フィードバック