Adjusting DCS Instance Bandwidth
Generally, Redis instances save and obtain data in the data layer closer to application services, which consumes the network bandwidth. Rate limits may occur when the instance bandwidth is insufficient, causing increased service latency or client connection exceptions. Currently, the Redis instance bandwidth can be adjusted on the console for DCS Redis 4.0 and later instances.
Notes and Constraints
- This function is unavailable for professional edition DCS Redis instances.
- This function is available only for instances in the Running state.
- The bandwidth adjustment range is from the instance's assured bandwidth to its maximum bandwidth. Generally, the maximum bandwidth per shard is 2048 Mbit/s when the physical machine of the instance node has sufficient bandwidths.
- The relationship between the instance bandwidth and the bandwidth of a single shard is as follows:
- Bandwidth of single-node or master/standby instances = Bandwidth per shard
- Bandwidth of read/write splitting instances = Bandwidth per shard × Replica quantity
- Bandwidth of cluster instances = Bandwidth per shard × Shard quantity, or the total bandwidth of all shards if the bandwidth per shard varies
Procedure
- Log in to the DCS console.
- Click in the upper left corner of the management console and select the region where your instance is located.
- In the navigation pane, choose Cache Manager.
- On the Cache Manager page, click the name of the DCS instance you want to configure.
- In the Instance Details area of the DCS instance, click Adjust Bandwidth next to Bandwidth.
Figure 1 Adjusting bandwidth
- On the Adjust Bandwidth page, set bandwidth parameters.
By default, the bandwidth can be manually adjusted. Enabling the auto scaling whitelist supports both Manual and Auto scaling. If the adjustment cannot be specified on the console, contact customer service.
- Set the bandwidth to a multiple of 8 within the valid range. Otherwise, a value rounded down to a multiple of 8 will be automatically used after the order is submitted. For example, if you set the bandwidth to 801, 800 will be used instead.
- Price shown on the change page is only the fee of the additional bandwidth.
- The additional bandwidth is pay-per-use.
- You can adjust the bandwidth whenever as required. If you perform multiple bandwidth changes in a billing period (one hour), you will be billed according to highest bandwidth in the period. For example, if you have changed the bandwidth of a DCS Redis instance from 256 Mbit/s (default) to 2048 Mbit/s, and changed the bandwidth again to 512 Mbit/s in the same billing period, you will be billed at the price of 2048 Mbit/s bandwidth.
- Manual
- Auto scaling
Enable Auto Bandwidth Increase and set the policies as required, as shown in Table 1.
Bandwidth increases automatically (up to 2,048 Mbit/s per shard) based on scaling policies. Automatic scaling overrides manual adjustments.Table 1 Setting auto bandwidth increase policies Policy
Description
Burst Bandwidth Usage ≥
Burst bandwidth usage threshold for bandwidth increases.
For example, if this policy is set to 70%, the shard bandwidth will be automatically increased when the burst bandwidth usage reaches 70%.
Monitoring Period
Monitoring period of bandwidth increases, in minutes. Default: 1
For example, if the monitoring period is set to 1 minute, the bandwidth data is monitored within 1 minute.
Silence
Interval between increases, in seconds. Default: 0
The silence time avoids consecutive automatic bandwidth increases.
- Confirm the bandwidth and fees, check Authorization, and click Submit.
When the bandwidth adjustment task is in the Successful state, the new bandwidth is used.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot