Help Center/ Distributed Cache Service/ FAQs/ Instance Scaling and Upgrade/ What DCS Instance Type Changes Are Supported?
Updated on 2024-06-19 GMT+08:00
View PDF

What DCS Instance Type Changes Are Supported?

Table 1 Instance type change options supported by different DCS instances

Version

Supported Type Change

Precautions

Redis 4.0/5.0

From master/standby or read/write splitting to Proxy Cluster
  1. Before changing the instance type to Proxy Cluster, evaluate the impact on services. For details, see What Are the Constraints on Implementing Multi-DB on a Proxy Cluster Instance? and Command Restrictions.
  2. Memory usage must be less than 70% of the maximum memory of the new flavor.
  3. Some keys may be evicted if the current memory usage exceeds 90% of the total.
  4. After the change, create alarm rules again for the instance.
  5. For instances that are currently master/standby, ensure that their read-only IP address or domain name is not used by your application.
  6. If your application cannot reconnect to Redis or handle exceptions, you may need to restart the application after the change.
  7. Modify instance specifications during off-peak hours. An instance is temporarily interrupted and remains read-only for about 1 minute during the specification change.

From Proxy Cluster to master/standby or read/write splitting

For details about the commands supported by different types of instances, see Command Compatibility.

Any instance type changes not listed in the preceding table are not supported. To modify specifications while changing the instance type, see IP Switching.

To check whether you can change the instance type of an instance, see the parameters displayed on the Modify Specifications page on the DCS console.