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

Billing Overview

PDF
포커스 모드
폰트 크기
마지막 업데이트 시간: 2024-09-24 16:54:22

Billing Mode

EMR on TKE clusters support the pay-as-you-go mode. The cluster usage fees consist of the EMR service fees, the POD resource fees in the TKE cluster used for deployment services, and other associated cloud product fees.
Note
The EMR on TKE cluster price inquiry only displays the EMR service fees, fees for TencentDB for MySQL, and CBS fees. It does not include the TKE resource deployment fees and other associated cloud product fees.

Billing Items

The EMR on TKE cluster instance fees include all EMR service fees, TKE resource fees, and associated cloud product fees within the cluster. During usage, other cloud product resources such as EIP, TencentDB for MySQL, CBS, CHDFS, COS, and VPC may be used. These will be charged according to the respective billing methods for each cloud product. For detailed fee information, see the billing descriptions of each product.
Fee Types
Billing Items
Fee Description
EMR Product Fees
Service Fees
Provide multi-dimensional management services for clusters, including page display and control, monitoring and alarm, job management, automated Ops, and other services. The service fees are calculated hourly based on the specifications and number of POD resources in the cluster. Tencent Cloud: CPU: USD 0.004617 per core per hour; Memory: USD 0.00192375 per GB per hour
TKE Resource Fees
POD Resource Fees
The resources for service roles are provided by underlying containers for deployment, supporting both TKE Standard and TKE Serverless clusters. By scheduling container resources during off-peak hours relative to online services, it enables hybrid operations of both offline and online tasks, improving machine utilization. For more details, see the TKE Standard Cluster Billing Overview and TKE Serverless Cluster Billing Overview.
Associated Cloud Product Fees
CLB
Some service roles support cross-container cluster access. When external access is enabled, one or more CLB instances are created, incurring corresponding fees. For detailed fee information, see the CLB Billing Overview. Both private network LB and public network LB access methods are supported.
TencentDB for MySQL
When one or more components such as Hive (local deployment), Hue, Ranger, Oozie, Druid, or Superset are deployed, a TencentDB for MySQL instance is required for metadata storage. The TencentDB for MySQL instance is purchased together with the cluster, and a corresponding order is generated for TencentDB for MySQL. The billing mode for TencentDB for MySQL is consistent with the cluster’s billing mode. For more details, see the TencentDB for MySQL Billing Overview and Cloud Database TencentDB for MySQL Pricing.
CBS
CBS provides data storage for containers. When the Create a PVC option is selected, at least one CBS volume needs to be purchased as a storage unit. The CBS fees are paid together with the cluster, and a corresponding order is generated on the CBS side. The billing mode for CBS is consistent with the cluster’s billing mode. For more details, see the Cloud Block Storage Billing Overview.
COS
When COS is used to implement compute-storage separation for the cluster, data storage and request fees are incurred as the cluster retrieves data from COS in response to compute requests. Additionally, new data may be generated in COS for purposes such as storing results or backups during computation. For more details, see the Cloud Object Storage Billing Overview and Cloud Object Storage Pricing.
CHDFS
When CHDFS is used to implement compute-storage separation for the cluster, data storage and request fees are incurred as the cluster retrieves data from CHDFS in response to compute requests. Additionally, new data may be generated in CHDFS for purposes such as storing results or backups during computation. For more details, see the Cloud HDFS Purchase Guide.


도움말 및 지원

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

피드백