Changes the configurations of an AnalyticDB for MySQL Data Lakehouse Edition cluster.
Operation description
- During a scaling event, you are not allowed to execute the
SUBMIT JOBstatement to submit asynchronous jobs. If your business requires asynchronous jobs, perform scaling during appropriate periods. - When you scale a cluster, data in the cluster is migrated for redistribution. The amount of time that is required to migrate data is proportional to the data volume. During a scaling event, the services provided by the cluster are not interrupted. When you downgrade cluster specifications, data migration may require up to dozens of hours to complete. Proceed with caution especially if your cluster contains a large amount of data.
- If the cluster has a built-in dataset loaded, make sure that the cluster has reserved storage resources of at least 24 AnalyticDB compute units (ACUs). Otherwise, the built-in dataset cannot be used.
- When the scaling process is about to end, transient connections may occur. We recommend that you scale your cluster during off-peak hours or make sure that your application is configured to automatically reconnect to your cluster.
- You can change an AnalyticDB for MySQL cluster from Data Warehouse Edition to Data Lakehouse Edition, but not the other way around. For more information, see Change a cluster from Data Warehouse Edition to Data Lakehouse Edition.
- For information about the endpoints of AnalyticDB for MySQL, see Endpoints .
Debugging
Authorization information
The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:
- Operation: the value that you can use in the Action element to specify the operation on a resource.
- Access level: the access level of each operation. The levels are read, write, and list.
- Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
- For mandatory resource types, indicate with a prefix of * .
- If the permissions cannot be granted at the resource level,
All Resourcesis used in the Resource type column of the operation.
- Condition Key: the condition key that is defined by the cloud service.
- Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
| Operation | Access level | Resource type | Condition key | Associated operation |
|---|---|---|---|---|
| adb:ModifyDBCluster | update | *DBClusterLakeVersion 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 Lakehouse Edition cluster. Note
You can call the DescribeDBClusters operation to query the IDs of all AnalyticDB for MySQL Data Lakehouse Edition clusters within a region.
| amv-bp1r053byu48p**** |
| RegionId | string | No | The region ID of the cluster. Note
You can call the DescribeRegions operation to query the most recent region list.
| cn-hangzhou |
| StorageResource | string | No | The reserved storage resources. Valid values: 0ACU to 2064ACU. The value must be in increments of 24ACU. Each ACU is approximately equal to 1 core and 4 GB memory. Note
This parameter must be specified with a unit.
| 24ACU |
| ComputeResource | string | No | The reserved computing resources. Valid values: 0ACU to 4096ACU. The value must be in increments of 16ACU. Each ACU is approximately equal to 1 core and 4 GB memory. Note
This parameter must be specified with a unit.
| 16ACU |
| EnableDefaultResourcePool | boolean | No | Specifies whether to allocate all reserved computing resources to the user_default resource group. Valid values:
| true |
Response parameters
Examples
Sample success responses
JSONformat
{
"RequestId": "0D6BF3E2-41D8-57F6-9A62-A13A70377952",
"DBClusterId": "amv-bp1r053byu48p****",
"OrderId": "2035629****"
}Error codes
| HTTP status code | Error code | Error message | Description |
|---|---|---|---|
| 400 | ACS.Cluster.InvalidWorkerState | The state of the worker does not support this operation. | This operation is not supported due to the current state of the storage node. |
| 400 | ACS.Cluster.ElasticPlanJobsExists | Operation failed. Ongoing elastic plan jobs exist. | Failed to perform this operation because a storage scaling plan job is running. |
For a list of error codes, visit the Service error codes.
Change history
| Change time | Summary of changes | Operation |
|---|---|---|
| 2024-09-18 | The Error code has changed. The request parameters of the API has changed | View Change Details |
| 2024-05-09 | The Error code has changed. The request parameters of the API has changed | View Change Details |
| 2023-07-27 | The Error code has changed. The request parameters of the API has changed | View Change Details |
| 2023-06-21 | The Error code has changed. The request parameters of the API has changed | View Change Details |
| 2023-05-09 | The Error code has changed. The request parameters of the API has changed | View Change Details |
| 2023-04-13 | The Error code has changed | View Change Details |