AnalyticDB for MySQL allows you to scale up cluster resources. You can use elastic plans to scale up resources at a scheduled point in time and then scale them back at a specified restoration point in time. This feature can meet the requirements for regular resource changes during peak and off-peak hours to make full use of resources. This topic describes how to scale up resources.
Prerequisites
The AnalyticDB for MySQL cluster must meet the following requirements:
- The edition of the cluster is Elastic mode for Cluster Edition.
- The cluster has 32 or more cores.
- The minor engine version of the cluster is 3.1.3.2 or later.
Note
- To upgrade the minor engine version, Submit a ticket.
- For more information about cluster editions and specifications, see Editions.
Effective time of an elastic plan
After you create or modify an elastic plan, the system determines the effective time of the plan based on the time when the plan is created or modified. The following table describes the effective time rules of the elastic plan.
Creation or modification time | Effective time | Example |
---|---|---|
00:00~23:00 | The elastic plan becomes effective at 00:00 the next day and is executed at the specified time after it becomes effective. | Example 1:
|
23:00~23:59 | The elastic plan becomes effective at 00:00 on the third day and is executed at the specified time after it becomes effective. | Example 2:
|