All Products
Search
Document Center

AnalyticDB for MySQL:ModifyElasticPlan

最終更新日:Jul 08, 2024

Modifies a scaling plan for an AnalyticDB for MySQL Data Lakehouse Edition (V3.0) cluster.

Operation description

For information about the endpoints of AnalyticDB for MySQL, see Endpoints.

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer.

Authorization information

There is currently no authorization information disclosed in the API.

Request parameters

ParameterTypeRequiredDescriptionExample
ElasticPlanNamestringYes

The name of the scaling plan.

Note You can call the DescribeElasticPlans operation to query the names of scaling plans.
test
StartTimestringNo

The start time of the scaling plan.

Note Specify the time in the ISO 8601 standard in the yyyy-MM-ddTHH:mm:ssZ format. The time must be in UTC.
2022-01-01T12:01:00Z
EndTimestringNo

The end time of the scaling plan.

Note Specify the time in the ISO 8601 standard in the yyyy-MM-ddTHH:mm:ssZ format. The time must be in UTC.
2025-01-01T12:01:00Z
CronExpressionstringNo

A CORN expression that specifies the scaling cycle and time for the scaling plan.

0 20 14 * * ?
TargetSizestringNo

The desired specifications of elastic resources after scaling.

Note
  • If the scaling plan uses EIUs and Default Proportional Scaling for EIUs is enabled, you do not need to specify this parameter. In other cases, you must specify this parameter.

  • You can call the DescribeElasticPlanSpecifications operation to query the specifications that are supported for scaling plans.

32ACU
DBClusterIdstringYes

The cluster ID.

Note You can call the DescribeDBClusters operation to query the IDs of all AnalyticDB for MySQL Data Lakehouse Edition (V3.0) clusters within a region.
amv-wz9509beptiz****

Response parameters

ParameterTypeDescriptionExample
object

The response parameters.

RequestIdstring

The request ID.

A5C433C2-001F-58E3-99F5-3274C14DF8BD

Examples

Sample success responses

JSONformat

{
  "RequestId": "A5C433C2-001F-58E3-99F5-3274C14DF8BD"
}

Error codes

HTTP status codeError codeError messageDescription
404InvalidDBCluster.NotFoundThe DBClusterId provided does not exist in our records.The specified DBClusterId parameter does not exist. Make sure that the DBClusterId value is valid.

For a list of error codes, visit the Service error codes.

Change history

Change timeSummary of changesOperation
2023-12-12The Error code has changedView Change Details
2023-04-13The Error code has changedView Change Details