Restarts an ApsaraDB for MongoDB instance.
Operation description
This operation can also be used to restart an instance, or restart a shard or mongos node in a sharded cluster instance.
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 |
---|---|---|---|---|
dds:RestartDBInstance | update |
|
| none |
Request parameters
Parameter | Type | Required | Description | Example |
---|---|---|---|---|
DBInstanceId | string | Yes | The instance ID. | dds-bpxxxxxxxx |
NodeId | string | No | The ID of the shard or mongos node in the sharded cluster instance. Note
The sharded cluster instance is restarted if you do not specify this parameter.
| d-bpxxxxxxxx |
Response parameters
Examples
Sample success responses
JSON
format
{
"RequestId": "149C517D-B586-47BE-A107-8673E0ED77C6"
}
Error codes
For a list of error codes, visit the Service error codes.
Change history
Change time | Summary of changes | Operation |
---|---|---|
2023-07-13 | The internal configuration of the API is changed, but the call is not affected | View Change Details |