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

M Node Overview

PDF
フォーカスモード
フォントサイズ
最終更新日: 2026-01-14 15:26:39

Overview

Managed Node (M Node) is a fully managed node rolled out by Elastic MapReduce (EMR) to achieve full cloud-native transformation, featuring fully automated Ops, security and reliability, and low costs. It only supports monthly subscription and pay-as-you-go billing modes. Compared with a host, it helps customers save about 30% of costs on average. It can be used to deploy compute nodes (task nodes) of EMR on CVM.
Note:
1. M Node does not support node login and the selection of placement groups.
2. When you create a cluster task node, you cannot select M Node. It is recommended to deploy the task type M Node through scale-out after the cluster is created.
3. You can purchase and use M nodes only in EMR-2.7.0, EMR-3.4.0, EMR-3.5.0, and EMR-3.6.0.

Directions

Manually Scaling Out M Nodes

1. Log in to EMR console, and click the ID or name of the target cluster in the cluster list to go to the details page of the cluster.
2. Choose Cluster Resources > Resource Management > Scale Out on the cluster details page. Select M Node for the Resource Type parameter and Task for the Scale-Out Node parameter, and specify the Fee Mode, Optional Services for Scale-Out, Scale-Out Quantity, and other parameters based on your business requirements. For details, see Cluster Scale-Out.

Automatically Scaling and Deploying M Nodes

M Node supports 3 scaling methods including custom scaling, scaling by scaling group, and managed scaling, which have differences in resource specification settings. You can preset the specifications of Host and M Node resources at the same time.
1. Log in to EMR console, and click the ID or name of the target cluster in the cluster list to go to the auto-scaling page of the cluster.
2. Enable the auto-scaling feature, select the corresponding scaling method, and set scaling specifications according to the corresponding method.
Custom scaling: Choose Basic Settings > Edit > Resource Type, and select M Node and Host or only select M Node.
Scaling by scaling group: Choose Add Scaling Group > Resource Type, and select M Node and Host or only select M Node. Choose Scaling specification > Add specification, and select M Node or Host when you add specifications at a time.
Managed scaling: Custom scaling: Choose Basic Settings > Edit > Resource Type, and select M Node and Host or only select M Node.
Notes:
1. When you set the Resource Type to M Node: Only M Node is supported when you add specifications in scaling specifications management. M Node specifications do not support spot instance billing.
2. When you set the Resource Type to M Node and Host: You need to select M Node or Host when you add specifications in scaling specifications management at one time. Only host resources support spot instance billing.
3. Resources of the same type support mixed delivery to meet the quantity requirement for scale-out. However, mixed delivery of Host and M Node is not supported. For details, see Practical Tutorial on Setting Scaling Rules.

M Node List Price

M Node standard nodes, M Node computing nodes, and M Node memory nodes are commercially available. You can purchase nodes both in the Chinese site and the International site. The prices of nodes with a single CPU core and single memory are the same in different AZs. For detailed prices of specific specifications, see EMR Product Pricing.
For example, an enterprise switches from the HOST-standard SA4 model (8 cores, 16 GB) to the M Node-standard type for deploying compute nodes. 30 nodes are used each day, and during the peak business hours of 3 hours each day, mainly from 8 PM to 11 PM, 20 nodes are required. The cost reduction for customers is calculated as follows:
Monthly subscription costs = Monthly subscription list price per node x Quantity
Pay-as-you-go cost = Pay-as-you-go list price per node x Quantity x Duration x 30 (days)
Billing/Resource Type
Monthly Subscription Cost (CNY/Month)
Pay-as-You-Go Cost (CNY/Month)
Comprehensive Cost (CNY/Month)
HOST-standard SA4
750.72*30=22521.6
1.46*20*3*30=2628
22521.6+2628=25149.6
M Node-standard type
542.72*30=16281.6
1.06*20*30=636
16281.6+636=16917.6
Comprehensive cost reduction
32.7%
Note:
1. The prices of M Node resources vary in different regions. For actual pricing and cost reduction granularity, the actual price prevails.
2. The above data is only calculation data, excluding disk price information.

ヘルプとサポート

この記事はお役に立ちましたか?

フィードバック