Deletes a read-only node from a PolarDB cluster.
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:
- The required resource types are displayed in bold characters.
- If the permissions cannot be granted at the resource level,
All Resources
is 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 |
---|---|---|---|---|
polardb:DeleteDBNodes | delete |
|
| none |
Request parameters
Parameter | Type | Required | Description | Example |
---|---|---|---|---|
DBClusterId | string | Yes | The ID of the cluster. | pc-************** |
ClientToken | string | No | The client token that is used to ensure the idempotence of the request. You can use the client to generate the value, but you must make sure that it is unique among different requests. The token can contain only ASCII characters and cannot exceed 64 characters in length. The token is case-sensitive. | 6000170000591aed949d0f54a343f1a42*********** |
DBNodeType | string | No | The type of the node. Valid values:
Enumeration Value:
| RO |
DBNodeId | array | Yes | The IDs of the nodes. Note
You can call the DescribeDBClusters operation to query the details of all clusters that belong to your Alibaba Cloud account, such as the cluster ID.
| |
string | Yes | The ID of the node. N is a positive integer that starts from 1. The maximum value of N is the number of current nodes minus 2. Each cluster must contain at least one primary node and one read-only node. Note
You can delete multiple read-only nodes at the same time only in PolarDB for MySQL clusters
| pi-**************** |
Response parameters
Examples
Sample success responses
JSON
format
{
"RequestId": "6566B2E6-3157-4B57-A693-AFB751******",
"DBClusterId": "pc-**************",
"OrderId": "2035638*******"
}
Error codes
HTTP status code | Error code | Error message | Description |
---|---|---|---|
400 | InvalidDBNodeNum.Malformed | The number of parameter DBNode.N is not valid. | The specified number of database nodes is invalid. |
400 | OperationDenied.DeleteDBNodesWithStrictConsistencyOn | 3AZ cluster does not allow delete db nodes. | Nodes cannot be deleted for multi-zone clusters. |
400 | InvalidDBNode.Malformed | The specified parameter DBNode.N is not valid. | The specified DBNode.N parameter is invalid. |
403 | OperationDenied.DBNodeRole | The operation is not permitted due to the role of node. | This operation is not supported by the node role. |
404 | InvalidDBClusterId.NotFound | The DBClusterId provided does not exist in our records. | The specified DBClusterId parameter does not exist in the current record. |
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 |
---|---|---|
2023-09-12 | The Error code has changed | View Change Details |
2023-06-20 | The Error code has changed. The request parameters of the API has changed | View Change Details |