ModifyDBClusterServerlessConf - PolarDB - Alibaba Cloud Documentation Center

This topic is generated by a machine translation engine without any human intervention. ALIBABA CLOUD DOES NOT GUARANTEE THE ACCURACY OF MACHINE TRANSLATED CONTENT. To request a human-translated version of this topic or provide feedback on this translation, please include it in the feedback form.

Modifies the configurations of a serverless cluster.

Debugging

You can run this interface directly in OpenAPI Explorer, saving you the trouble of calculating signatures. After running successfully, OpenAPI Explorer can automatically generate SDK code samples.

Debug

Authorization information

There is currently no authorization information disclosed in the API.

Request parameters

Parameter	Type	Required	Description	Example
DBClusterId	string	Yes	The ID of the serverless cluster.	pc-bp10gr51qasnl****
ScaleMin	string	No	The minimum number of PCUs per node for scaling. Valid values: 1 PCU to 31 PCUs.	1
ScaleMax	string	No	The maximum number of PCUs per node for scaling. Valid values: 1 PCU to 32 PCUs.	10
ScaleRoNumMin	string	No	The minimum number of read-only nodes for scaling. Valid values: 0 to 15.	1
ScaleRoNumMax	string	No	The maximum number of read-only nodes for scaling. Valid values: 0 to 15.	2
AllowShutDown	string	No	Specifies whether to enable No-activity Suspension. Default value: false. Valid values: true false	true
SecondsUntilAutoPause	string	No	The detection period for No-activity Suspension. Valid values: 5 to 1440. Unit: minutes. The detection duration must be a multiple of 5 minutes.	10
ScaleApRoNumMin	string	No	The minimum number of stable AP read-only nodes. Valid values: 0 to 7.	1
ScaleApRoNumMax	string	No	The maximum number of stable AP read-only nodes. Valid values: 0 to 7.	1
PlannedStartTime	string	No	The earliest start time of the scheduled task for adding the read-only node. The scheduled task specifies that the task is run in the required period. Specify the time in the YYYY-MM-DDThh:mm:ssZ format. The time must be in UTC. Note The earliest start time of the scheduled task can be a point in time within the next 24 hours. For example, if the current time is `2021-01-14T09:00:00Z`, you can specify a point in time between `2021-01-14T09:00:00Z` and `2021-01-15T09:00:00Z`. If you leave this parameter empty, the task for adding the read-only node is immediately run by default.	2021-01-14T09:00:00Z
PlannedEndTime	string	No	The latest start time for upgrading the specifications within the scheduled time period. Specify the time in the YYYY-MM-DDThh:mm:ssZ format. The time must be in UTC. Note The value of this parameter must be at least 30 minutes later than the value of PlannedStartTime. If you specify PlannedStartTime but do not specify PlannedEndTime, the latest start time of the task is set to a value that is calculated by using the following formula: `PlannedEndTime value + 30 minutes`. For example, if you set PlannedStartTime to `2021-01-14T09:00:00Z` and you do not specify PlannedEndTime, the latest start time of the task is set to `2021-01-14T09:30:00Z`.	2021-01-14T09:30:00Z
FromTimeService	boolean	No	Specifies an immediate or scheduled task to modify parameters and restart the cluster. Valid values: false: scheduled task true: immediate task	false
ServerlessRuleCpuShrinkThreshold	string	No	CPU downscale threshold	50
ServerlessRuleCpuEnlargeThreshold	string	No	CPU burst threshold	80
ServerlessRuleMode	string	No	Elastic sensitivity. Values: - normal: standard - flexible: sensitive	normal flexible
TaskId	string	No	Asynchronous task ID.	143f8e9f-2566-4dff-be47-bed79f28fc78
CrontabJobId	string	No	Cycle policy ID.	143f8e9f-2566-4dff-be47-bed79f28fc78

Response parameters

Parameter	Type	Description	Example
	object
DBClusterId	string	The ID of the serverless cluster.	pc-bp10gr51qasnl****
RequestId	string	The ID of the request.	5E71541A-6007-4DCC-A38A-F872C31FEB45

Examples

Sample success responses

JSONformat

{
  "DBClusterId": "pc-bp10gr51qasnl****",
  "RequestId": "5E71541A-6007-4DCC-A38A-F872C31FEB45"
}

Error codes

HTTP status code	Error code	Error message	Description
404	InvalidDBInstanceClass.NotFound	rw class code must be equal with hot replica	The specification of the secondary node must be the same as that of the primary node.
404	InvalidDBClusterId.Malformed	The specified parameter DBClusterId is not valid.	The specified DBClusterId parameter is invalid.

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

Change history

Change time	Summary of changes	Operation
2024-05-17	The Error code has changed. The request parameters of the API has changed	View Change Details
2023-09-25	The Error code has changed. The request parameters of the API has changed	View Change Details
2023-09-21	The Error code has changed. The request parameters of the API has changed	View Change Details
2023-04-24	The Error code has changed. The request parameters of the API has changed	View Change Details