Modify a scheduled scaling plan using ModifyElasticPlan - AnalyticDB - Alibaba Cloud - AnalyticDB

Modifies a scheduled scaling plan for AnalyticDB for MySQL clusters in elastic mode for Cluster Edition.

Operation description

This operation applies only to AnalyticDB for MySQL Data Warehouse Edition (V3.0) clusters in elastic mode for Cluster Edition that have 32 cores or more.

Try it now

Try this API in OpenAPI Explorer, no manual signing needed. Successful calls auto-generate SDK code matching your parameters. Download it with built-in credential security for local usage.

Test

RAM authorization

The table below describes the authorization required to call this API. You can define it in a Resource Access Management (RAM) policy. The table's columns are detailed below:

Action: The actions can be used in the Action element of RAM permission policy statements to grant permissions to perform the operation.
API: The API that you can call to perform the action.
Access level: The predefined level of access granted for each API. Valid values: create, list, get, update, and delete.
Resource type: The type of the resource that supports authorization to perform the action. It indicates if the action supports resource-level permission. The specified resource must be compatible with the action. Otherwise, the policy will be ineffective.
- For APIs with resource-level permissions, required resource types are marked with an asterisk (*). Specify the corresponding Alibaba Cloud Resource Name (ARN) in the Resource element of the policy.
- For APIs without resource-level permissions, it is shown as All Resources. Use an asterisk (*) in the Resource element of the policy.
Condition key: The condition keys defined by the service. The key allows for granular control, applying to either actions alone or actions associated with specific resources. In addition to service-specific condition keys, Alibaba Cloud provides a set of common condition keys applicable across all RAM-supported services.
Dependent action: The dependent actions required to run the action. To complete the action, the RAM user or the RAM role must have the permissions to perform all dependent actions.

Action

Access level

Resource type

Condition key

Dependent action

adb:ModifyElasticPlan

update

DBCluster

acs:adb:{#regionId}:{#accountId}:dbcluster/{#DBClusterId}

None

Request parameters

Parameter	Type	Required	Description	Example
DBClusterId	string	Yes	The ID of the AnalyticDB for MySQL Data Warehouse Edition (V3.0) cluster. Note You can call the DescribeDBClusters operation to query the cluster IDs of all AnalyticDB for MySQL Data Warehouse Edition (V3.0) clusters within a region.	am-bp1rqvm70uh2v****
ElasticPlanName	string	Yes	The name of the scaling plan. The name must be 2 to 30 characters in length. The name can contain letters, digits, and underscores (_). Note You can call the DescribeElasticPlan operation to query scaling plans of a cluster, including their names.	realtime
ResourcePoolName	string	No	The name of the resource group. Note You can call the DescribeDBResourceGroup operation to query the resource group name.	test
ElasticPlanNodeNum	integer	No	The number of nodes in the scaling plan. If ElasticPlanType is set to worker, you can set this parameter to 0 or leave this parameter empty. If ElasticPlanType is set to executorcombineworker or executor, you must set this parameter to a value that is greater than 0.	0
ElasticPlanTimeStart	string	No	The scale-up time of the scaling plan. Specify the time on the hour in the HH:mm:ss format.	8:00:00
ElasticPlanTimeEnd	string	No	The restoration time of the scaling plan. Specify the time on the hour in the HH:mm:ss format. The interval between the scale-up time and the restoration time cannot exceed 24 hours.	10:00:00
ElasticPlanWeeklyRepeat	string	No	The days of the week to execute the scaling plan. Valid values: 0 to 6, which indicate Sunday to Saturday. Separate multiple values with commas (,).	1,2,3,4,5
ElasticPlanMonthlyRepeat	string	No	The dates of the month to execute the scaling plan. Each number specifies a date. Separate multiple values with commas (,).	1,15,25
ElasticPlanStartDay	string	No	The start date of the scaling plan. Specify the date in the yyyy-MM-dd format.	2022-12-02
ElasticPlanEndDay	string	No	The end date of the scaling plan. Specify the date in the yyyy-MM-dd format.	2022-12-09
ElasticPlanEnable	boolean	No	Specifies whether to enable the scaling plan. Valid values: true (default) false	true
ElasticPlanType	string	No	The type of the scaling plan. Valid values: worker: scales only elastic I/O resources. executor: scales only computing resources. executorcombineworker (default): scales both elastic I/O resources and computing resources by proportion. Note If you want to set this parameter to executorcombineworker, make sure that the cluster runs a minor version of 3.1.3.2 or later. If you want to set this parameter to worker or executor, make sure that the cluster runs a minor version of 3.1.6.1 or later and a ticket is submitted. After your request is approved, you can set this parameter to worker or executor.	worker
ElasticPlanWorkerSpec	string	No	The resource specifications for scale-up. Valid values: 8 Core 64 GB (default) 16 Core 64 GB 32 Core 64 GB 64 Core 128 GB 12 Core 96 GB 24 Core 96 GB 52 Core 86 GB	16 Core 64 GB

Response elements

Element	Type	Description	Example
	object	The response parameters.
RequestId	string	The request ID.	1AD222E9-E606-4A42-BF6D-8A4442913CEF

Examples

Success response

JSON format

{
  "RequestId": "1AD222E9-E606-4A42-BF6D-8A4442913CEF"
}

Error codes

HTTP status code	Error code	Error message	Description
400	ElasticPlanParameterError	The specified elastic plan parameter is invalid.	The specified elastic plan parameter is invalid.
404	InvalidDBCluster.NotFound	The DBClusterId provided does not exist in our records.	The specified DBClusterId parameter does not exist. Make sure that the DBClusterId value is valid.

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.