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

Practical Tutorial on Setting Time-based Scaling Rules

PDF
포커스 모드
폰트 크기
마지막 업데이트 시간: 2025-01-03 15:05:10
Based on the clear peaks and valleys in business activity over a certain period, you can choose between setting the execution frequency to Repeat or Execute only once. Configure scale-out rules and scale-in rules accordingly. When choosing Repeat, you can set the rule’s effective deadline by configuring the rule’s validity period, after which the scaling rules will no longer be triggered.
Example:
Your business activity starts increasing at 10 PM and begins to decrease at 6 AM daily, and this pattern is expected to last for one month. You can configure a time-based policy by setting up two scaling rules (one for scale-out and one for scale-in) or a single scale-out rule with scheduled termination.
Scaling Rule: Set to repeat daily. Configure the scale-out rule to be triggered at 10 PM each day for one month.
Scaling-down rule: Set to repeat daily. Configure the scale-in rule to be triggered at 6 AM each day for one month.
Scaling Rule + Scheduled Termination:scheduled termination: Set to repeat daily. Configure the scale-out rule to be triggered at 10 PM each day, with the allocated resources scheduled for 8 hours of use (equivalent to terminating at 6 AM the next day). This configuration will continue for one month. Support for Daily, Weekly, or Monthly repetition is available, so adjust based on your actual requirements. For more details on other rule configuration items and usage, see Setting Time-Based Scaling.
Note:
1. The timing for adding resources to the cluster above represents an ideal scene. In practice, the actual scale-out time depends on the number of resources requested. It is recommended to set the time rules at least 5 minutes earlier based on your needs.
2. During peak periods, resource contention may prevent the actual scale-out number from reaching the elastic target number of machines. It is recommended to enable the Resource Replenishment Retry Policy for your scale-out rule.
3. When the scale-in action is triggered, nodes may still be executing tasks. To avoid immediate release of the nodes, it is recommended that you enable graceful scale-in. For more details, see Graceful Scale-In.

도움말 및 지원

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

피드백