This topic describes the different states of an ApsaraDB for Redis instance to help you manage your instances. When you change configurations or restart an instance, the status 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 status of an instance by using the following methods:

State in the ApsaraDB for Redis console Status returned by the API operation Operation that leads to the state 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 N/A 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 prevent resource waste.
Changing Configuration Changing Change the configurations of an instance For more information, see Change process and impact.
Restarting Rebooting Restart an instance The instance is 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
  • When you apply for resources, upgrade the replica node, or synchronize data, your ApsaraDB for Redis service remains available.
  • When you switch your workloads over from the original instance to a new instance or from the master node to the replica node in the original instance, you may experience transient connections that last a few seconds. The original instance stays in the read-only state within 60 seconds until all data is synchronized. We recommend that you upgrade the original instance during off-peak hours and make sure that your application is configured to automatically reconnect to the original instance.
  • If the original instance runs Redis 4.0, Bloom filter-related API operations, such as BF.ADD, are no longer supported after you upgrade the major version of the original instance to a version later than Redis 4.0.
    Notice Bloom filter-related API operations on existing instances of ApsaraDB for Redis 4.0 are only for internal use. In addition, new instances that run Redis 4.0 or later no longer support Bloom filter-related API operations. Therefore, if you call Bloom filter-related API operations, you cannot perform cache analytics and unknown errors may occur. We recommend that you change the edition of the original instance to ApsaraDB for Redis Enhanced Edition (Tair) to supports the optimized Bloom filter. For more information, see Performance-enhanced instances.
Upgrading Minor Version MinorVersionUpgrading Upgrade the minor version
Configuring Network NetworkModifying Change the network type from classic network to VPC
  • After you switch the network type of an ApsaraDB for Redis instance from classic network to VPC, you cannot switch back to classic network.
  • The instance is 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.
  • When you switch the network type, you can specify whether to retain the classic network endpoint of the instance. If you do not retain the classic network endpoint of the instance, the endpoint is released after the network type is switched. Then, clients cannot connect to the ApsaraDB for Redis instance by using the classic network endpoint. You must change the database connection string on your client at the earliest opportunity.
Change the endpoint or port number of an ApsaraDB for Redis instance Clients can no longer connect to the instance by using the original endpoints. Update the connection information on the clients at the earliest opportunity.
Apply for a public endpoint No impact.
Release public endpoints Clients can no longer connect to the instance by using the original public endpoint. Update the connection information on the clients at the earliest opportunity.
Enable the direct connection mode

If you enable the direct connection mode, you cannot perform the following operations:

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

Release a direction connection endpoint Clients can no longer connect to the instance by using the original direct connection endpoint. Update the connection information on the clients at the earliest opportunity.
Configuring SSL SSLModifying Configure SSL encryption for an ApsaraDB for Redis instance The instance restarts after you enable SSL encryption or update the certificate. The instance is 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 is 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 updates it to the latest version to ensure high performance and stability.
Restarting Rebooting Restart an instance The instance is 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 Delete data If you choose to delete all data, take note of the following impacts:
  • 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 If you choose to delete expired data, take note of the following impacts:
  • The instance runs the SCAN command to delete all 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 workloads over from a master node to a replica node
  • When you switch your workloads over from a master node to a replica node, the master node and the replica node are forced into the read-only state and transient connections occur. The read-only state and transient connections last a few minutes. Make sure that your applications are configured to automatically reconnect to the ApsaraDB for Redis instance.
  • If the ApsaraDB for Redis instance is in the Switching state, you cannot manage the instance. For example, you cannot change the specifications of the instance or migrate the instance to other zones.
Disabled Inactive N/A The instance expires and cannot provide database services. If you want to continue to use the instance, you must renew the instance. For more information, see Renew an instance.
Released N/A Manually or automatically release an instance that is overdue or expired The instance is released and cannot provide database services. The instance disappears from the Instances page. If you want to continue to use 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.