动态与公告

产品动态

产品公告

安全公告

产品简介

产品概述

产品优势

产品架构

产品功能

应用场景

约束与限制

技术支持范围

产品发行版

购买指南

EMR on CVM 计费说明

EMR on TKE 计费说明

EMR Serverless HBase 计费说明

快速入门

EMR on CVM 快速入门

EMR on TKE 快速入门

EMR on CVM 操作指南

规划集群

管理权限

配置集群

管理集群

管理服务

监控告警

智能管家

EMR on TKE 操作指南

EMR on TKE 简介

配置集群

管理集群

管理服务

监控运维

应用分析

EMR Serverless HBase 操作指南

EMR Serverless HBase 产品简介

配额与限制

规划实例

管理实例

监控告警

开发指南

EMR 开发指南

Hadoop开发指南

Spark 开发指南

HBASE开发指南

Phoenix on Hbase 开发指南

Hive 开发指南

Presto开发指南

Sqoop 开发指南

Hue 开发指南

Oozie 开发指南

Flume 开发指南

Kerberos 开发指南

Knox 开发指南

Alluxio 开发指南

Kylin 开发指南

Livy 开发指南

Kyuubi 开发指南

Zeppelin 开发指南

Hudi 开发指南

Superset 开发指南

Impala 开发指南

Druid 开发指南

Tensorflow 开发指南

Kudu 开发指南

Ranger 开发指南

Kafka 开发指南

Iceberg 开发指南

StarRocks 开发指南

Flink 开发指南

JupyterLab 开发指南

MLflow 开发指南

实践教程

EMR on CVM 运维实践

数据迁移实践

自定义伸缩实践教程

API 文档

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

常见问题

EMR on CVM常见问题

服务等级协议

联系我们

Scaling Group Configuration

聚焦模式

字号

最后更新时间： 2026-03-20 17:25:55

A scaling group adds scaling rules and scaling specifications. When a rule is triggered, the scaling group automatically scales out or scales in according to the preset strategy of the rule. If no rules and specifications are set, no scaling operation will be triggered.
Supports up to 10 scaling groups. Groups do not affect each other. Supports simultaneous scaling operations. Scaling within a single group follows the rule of "first triggered, first executed; if triggered simultaneously, executed according to rule priority".
Scaling Group Settings
Parameter Settings
Description
Name
In the same cluster, scaling group names are not allowed to be duplicated.
Maximum number of nodes
Used to control the upper limit of the number of nodes in the current scaling group; no scale-out will occur when the limit is reached.
Minimum number of nodes
Used to control the lower limit of the number of nodes in the current scaling group; no scale-in will occur when the limit is reached.
Note: When editing later, it cannot be less than the number of elastic nodes in the current scaling group.
Payment Method
Pay-as-you-go Billing: When the scale-out rule is triggered, all added pay-as-you-go nodes supplement computing power.
Bidding Instance Priority: When the scale-out rule is triggered, bidding instances are added first to supplement computing power. When bidding instance resources are insufficient, pay-as-you-go resources are used to make up for the computing power.
The HOST resource type supports pay-as-you-go billing and bidding instance billing, while the MNode and POD resources only support pay-as-you-go billing.
Spot instances support the repossession mechanism due to the limited availability of resources. We recommend you choose pay-as-you-go to ensure cluster computing power and avoid failures in supplementing computing power.
Minimum proportion of pay-as-you-go nodes: The minimum proportion of pay-as-you-go nodes to the scale-out quantity in a single scale-out. For example, if 10 nodes are to be added in a single scale-out and the minimum proportion of pay-as-you-go nodes is 20%, when the scale-out rule is triggered, at least 2 pay-as-you-go nodes will be added, and the remaining 8 nodes will be supplemented with spot instances. If spot instance resources are insufficient for 8 nodes, pay-as-you-go nodes will be used to make up the difference.
Node Label
By default, scale-out resources will be placed in the Default Label. After setting, scale-out resources will be put into the specified Label. When the scale-in rule is triggered, resources of the corresponding label will be scaled in; only capacity scheduling takes effect.
Scaling Specifications Management
Scaling specifications are used to specify the elastic scale-out node specifications. To maintain a linear change in cluster load, ensure that the CPU and memory of the scaling specifications are consistent.
1. Click Add Specifications. On the "Add Task Specifications" page, select resource type, model specifications, and other information to perform specifications settings.
2. You can add and delete the nodes in the scaling specifications, and adjust the priority of scaling specifications as needed. The priority order of specifications is from high to low (1＞2＞3＞4＞5).
Scaling Rule Management
For more information on how to set scaling rules and execution principles, see  Scaling Rule Management.

帮助和支持

本页内容是否解决了您的问题？

您也可以联系销售或提交工单以寻求帮助。

填写满意度调查问卷，共创更好文档体验。

文档反馈

tencent cloud

弹性 MapReduce

Scaling Group Configuration

Scaling Group Settings

Scaling Specifications Management

Scaling Rule Management

帮助和支持

Parameter Settings	Description
Name	In the same cluster, scaling group names are not allowed to be duplicated.
Maximum number of nodes	Used to control the upper limit of the number of nodes in the current scaling group; no scale-out will occur when the limit is reached.
Minimum number of nodes	Used to control the lower limit of the number of nodes in the current scaling group; no scale-in will occur when the limit is reached. Note: When editing later, it cannot be less than the number of elastic nodes in the current scaling group.
Payment Method	Pay-as-you-go Billing: When the scale-out rule is triggered, all added pay-as-you-go nodes supplement computing power. Bidding Instance Priority: When the scale-out rule is triggered, bidding instances are added first to supplement computing power. When bidding instance resources are insufficient, pay-as-you-go resources are used to make up for the computing power. The HOST resource type supports pay-as-you-go billing and bidding instance billing, while the MNode and POD resources only support pay-as-you-go billing. Spot instances support the repossession mechanism due to the limited availability of resources. We recommend you choose pay-as-you-go to ensure cluster computing power and avoid failures in supplementing computing power. Minimum proportion of pay-as-you-go nodes: The minimum proportion of pay-as-you-go nodes to the scale-out quantity in a single scale-out. For example, if 10 nodes are to be added in a single scale-out and the minimum proportion of pay-as-you-go nodes is 20%, when the scale-out rule is triggered, at least 2 pay-as-you-go nodes will be added, and the remaining 8 nodes will be supplemented with spot instances. If spot instance resources are insufficient for 8 nodes, pay-as-you-go nodes will be used to make up the difference.
Node Label	By default, scale-out resources will be placed in the Default Label. After setting, scale-out resources will be put into the specified Label. When the scale-in rule is triggered, resources of the corresponding label will be scaled in; only capacity scheduling takes effect.