tencent cloud

Elastic MapReduce

ドキュメントElastic MapReduce EMR on CVM Operation GuideManaging ClusterAuto ScalingScaling Group Configuration

Scaling Group Configuration

PDF
フォーカスモード
フォントサイズ
最終更新日: 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.
前の記事へ: Custom Scaling Configuration次の記事へ: Managed Scaling Configuration

ヘルプとサポート

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

フィードバック