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

Introduction to EMR on TKE

PDF
포커스 모드
폰트 크기
마지막 업데이트 시간: 2024-10-30 10:45:22
Tencent Cloud EMR on TKE is a big data service deployment platform based on containerized services and open-source big data engines, offering rapid deployment, flexible scaling, and efficient, secure services. Through features like application management in the console, users can focus more on business applications. The service engine includes big data components such as Spark, Hive, and Trino, allowing users to easily run, manage, and scale containerized applications.

Product Architecture




Description
Data storage: In the compute-storage separation scene applicable to EMR on TKE, multiple data storage products such as COS, CHDFS, and HDFS are provided for integration. Users can store data in these sources and perform processing and analysis using the EMR on TKE big data processing engine.
Computing resources: EMR on TKE supports deployment on Tencent Cloud TKE General Clusters and Serverless Clusters.
Big data components: EMR on TKE provides optional services including Hive, Spark, Trino, Zookeeper, Kyuubi, Knox, Ranger, Hue, and RSS.
Management platform: EMR on TKE provides a user-friendly interface through the EMR console for easy component deployment, configuration management, Ops monitoring, and exception alerts. It also offers advanced job analysis and diagnostics to help users gain insights into job costs.

Product Advantages

1. High resource utilization: EMR on TKE container services can automatically scale the number of cluster containers up or down based on preset policies, ensuring stable service operation while saving on resource costs. Flexible application resource configuration in offline scenes effectively improves resource utilization and optimizes costs.
2. Stability and reliability: EMR on TKE relies on the high-reliability features of TKE clusters, such as container self-check and self-healing. When a service pod node fails, the pod is automatically rebuilt, and the image is reloaded.
3. Simplified deployment: EMR on TKE can start a complete multi-service cluster in just a few minutes. Additionally, it allows users to easily and quickly adjust the number of service pods through console operations.
4. Granular security: EMR on TKE integrates with CAM to implement cluster access control. It also connects with COS using minimized storage permissions to achieve refined permission management in compute-storage separation scenes, ensuring the security of data access at the cluster usage level.

도움말 및 지원

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

피드백