Temporarily adjusts the internal bandwidth of an ApsaraDB for Redis instance that is deployed in a dedicated cluster.
Operation description
- This operation is applicable only to an ApsaraDB for Redis instance that is deployed in a dedicated cluster. To adjust the bandwidth of a standard ApsaraDB for Redis instance, call the EnableAdditionalBandwidth operation.
Debugging
Authorization information
Request parameters
Parameter | Type | Required | Description | Example |
---|---|---|---|---|
InstanceId | string | Yes | The ID of the instance. | r-bp1zxszhcgatnx**** |
BandWidth | long | No | The amount of bandwidth that you want to add. Unit: Mbit/s. The value must be an integer greater than or equal to 0. In most cases, the maximum bandwidth that can be added can be two times the default maximum bandwidth of the current instance type. For more information about the bandwidth specifications supported by different instance types, see Overview . The bandwidth is also subject to the following limits:
Note
If you do not specify this parameter for a standard instance, the bandwidth of the instance is set to two times that of the current bandwidth.
| 10 |
NodeId | string | No | The ID of the data node. You can call the DescribeClusterMemberInfo operation to query the node ID. Separate multiple IDs with commas (,). Note
This parameter is available and required only when the instance uses the cluster architecture.
| r-bp1zxszhcgatnx****-db-0 |
Response parameters
Examples
Sample success responses
JSON
format
{
"RequestId": "97AC8948-D7E4-457E-BE03-850CF04E****"
}
Error codes
For a list of error codes, visit the Service error codes.