This topic describes the different states of an instance to help you manage your instances. When you change specifications or restart an ApsaraDB for Redis instance, the state of the instance changes. This may cause issues. For example, the instance may be disconnected for a few seconds.

Instance states

You can query the state of an instance by using the following methods:

Console API Operation Description
Creating Creating Create an instance After you create an instance, the instance enters the Running state. The instance cannot provide database services in this state.
Running Normal None The instance can provide database services in this state.
Converting Transforming Change the billing method to subscription After you change the billing method of the instance to subscription, you cannot change the billing method back to pay-as-you-go. Before you change the billing method, we recommend that you evaluate your business requirements to avoid resource waste.
Changing Configuration Changing

Change specifications

The instance may be disconnected one or two times within 30 seconds. We recommend that you perform this operation during off-peak hours and make sure that your application can automatically reconnect to the instance.
Restarting Rebooting Restart an instance The instance may be disconnected for a few seconds. We recommend that you perform this operation during off-peak hours and make sure that your application can automatically reconnect to the instance.
Updating MajorVersionUpgrading Upgrade the major version The instance may remain in the read-only state for 60 seconds until all data is synchronized. The service may be interrupted for a few seconds during this time period. We recommend that you perform this operation during off-peak hours and make sure that your application can automatically reconnect to the instance.
Upgrading Minor Version MinorVersionUpgrading Upgrade the minor version
Configuring Network NetworkModifying Change the network type from classic network to VPC
  • The instance may be disconnected for a few seconds. We recommend that you perform this operation during off-peak hours and make sure that your application can automatically reconnect to the instance.
  • After you change the network type to Virtual Private Cloud (VPC), you cannot change it back to classic network.
Modify endpoints The instance may be disconnected for a few seconds. We recommend that you perform this operation during off-peak hours and make sure that your application can automatically reconnect to the instance.
Apply for a public endpoint No impacts.
Release public endpoints Clients can no longer connect to the ApsaraDB for Redis instance by using the original public endpoint.
Enable the direct connect mode

If you enable the direct connect mode, you are not allowed to perform the following operations:

You must release the private endpoint before you can perform the preceding operations.

Release a private endpoint Clients can no longer connect to the ApsaraDB for Redis instance by using the original private endpoint.
Configuring SSL SSLModifying Configure SSL encryption The instance restarts after you enable SSL encryption and renew the certificate. The instance may be disconnected for a few seconds. We recommend that you perform this operation during off-peak hours and make sure that your application can automatically reconnect to the instance.
Migrating to Another Zone ZoneMigrating Migrate an instance across zones
  • The instance may be disconnected for a few seconds. We recommend that you perform this operation during off-peak hours and make sure that your application can automatically reconnect to the instance.
  • If the minor version of the instance is outdated, the system upgrades it to the latest version to ensure high performance and stability.
Restarting Rebooting Restart an instance The instance may be disconnected for a few seconds. We recommend that you perform this operation during off-peak hours and make sure that your application can automatically reconnect to the instance.
Flushing Instance Flushing Clear data
  • The instance runs the FLUSHALL command to delete all of the keys in the instance. The deleted keys cannot be recovered.
  • This operation immediately deletes all the keys in the instance and adversely affects your online services. Proceed with caution. We recommend that you perform this operation during off-peak hours.
Deleting Expired Data CleaningUpExpiredData Clear data
  • The instance runs the FLUSHALL command to delete all of the expired keys in the instance. The deleted keys cannot be recovered.
  • This operation immediately deletes all the expired keys in the instance and adversely affects your online services. Proceed with caution. We recommend that you perform this operation during off-peak hours.
Switching HASwitching Switch node roles The data nodes may change to the read-only state and become disconnected for a few seconds. We recommend that you perform this operation during off-peak hours and make sure that your application can automatically reconnect to the instance.
Disabled Inactive None The instance expires and cannot provide services. If you want to continue using the instance, you must renew the instance. For more information, see Renew an instance.
Released None Manually or automatically release an instance that is overdue or expired The instance is released and cannot provide services. The instance cannot be displayed on the Instances page. If you want to continue using the instance, you can find and restore the instance from the recycle bin. For more information, see Manage ApsaraDB for Redis instances in the recycle bin.