The cloud-native deployment mode is compatible with higher Redis versions and provides more flexible architecture configurations. You can refer to this topic to convert a classic instance into a cloud-native instance.
This feature is in public preview. To use this feature, submit a ticket.
Conversion process
When you change the configurations of an instance, the instance may experience a transient connection that lasts up to 30 seconds. Make sure that your application can automatically reconnect to the instance.
To synchronize incremental data from the original instance to the new instance and prevent dual writes caused by DNS cache, the instance remains read-only for up to 1 minute during the configuration change. This ensures data consistency between the new instance and the original instance. If a large amount of data is written to the instance, the instance may remain read-only for an extended period of time. Therefore, we recommend that you perform the configuration change during off-peak hours.
Limits
Billing requirements
Only pay-as-you-go instances are supported. Subscription instances need to be converted to pay-as-you-go instances.
Network configuration
Bandwidth adjustment
If you have manually adjusted the bandwidth, you must restore the instance to the default bandwidth.
If bandwidth auto scaling is enabled, you must disable bandwidth auto scaling.
Connection address: If you applied for a public or private endpoint for a cluster instance, you must release the endpoint.
Security configuration
To implement password-free access to an instance in a virtual private cloud (VPC), you must add the CIDR block of the VPC to the instance whitelist, and then modify the value of
#no_loose_check-whitelist-alwaystoyes.For an instance with a security group configured, you must add the CIDR block of the VPC to the whitelist, and then delete the security group before converting the instance to a cloud-native instance. After the conversion is complete, you can add the security group again.
Feature compatibility
Instances with multi-zone read/write splitting, transparent data encryption (TDE), or Global Distributed Cache enabled cannot be converted.
If Transport Layer Security (TLS) or data flashback is enabled, you must disable the feature first.
Precautions
After the conversion, the instance ID and endpoint remain unchanged, and the data in the instance is not lost.
If the original instance runs Redis 2.8 or Redis 4.0, we recommend that you upgrade the instance to Redis 5.0 before you perform the conversion.
Procedure
Log on to the console and go to the Instances page. In the top navigation bar, select the region in which the instance that you want to manage resides. Then, find the instance and click the instance ID.
In the Configuration Information section, click Change to Cloud-native.
NoteThis feature is in public preview. If you cannot find this button, submit a ticket.
Select the shard specifications and the number of shards after conversion.
We recommend that you select instance specifications that are the same as or higher than the specifications of the original instance.
Configure parameters such as Billing Method, Major Version, and Switching Time.
When you perform this operation, you can also choose to upgrade the instance to a higher version other than Redis 5.0, such as Redis 6.0 or Redis 7.0. For more information, see New features and compatibility changes of major versions of Redis Open-Source Edition.
Read and select the Service Agreement (and Conversion Notes), and then click Buy Now.
The instance status changes to Changing Architecture Type. When the instance status changes to Running, the configuration change is complete.
FAQ
Q: Why does the The requested instance has insufficient capacity error message appear?
A: This error message indicates that cloud-native resources are insufficient in the zone where the original instance is located. This situation may occur if the original instance was created a long time ago. You can migrate the instance to another zone and then try again.
Q: After the configuration change is complete, why does the connection to the instance using DMS fail?
A: You need to add the IP address of DMS to the whitelist.