This topic describes the different states of an ApsaraDB for Redis instance to help you manage your instances. When you restart or change the configurations of an instance, the state of the instance changes. This may cause issues. For example, a transient connection within seconds occurs on the instance.
Instance states
You can query the state of an instance by using the following methods:
- Use the ApsaraDB for Redis console: You can view the state of instances on the Instances page of the ApsaraDB for Redis console.
- Call an API operation: You can call the DescribeInstances operation to query the state of an instance.
State in the console | State returned by calling the API operation | Operation that leads to the state | Description |
---|---|---|---|
Creating | Creating | Step 1: Create an ApsaraDB for Redis instance | After you create an instance, the instance enters the state. The instance cannot provide database services until the instance enters the Running 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 make better use of the instance. |
Changing Configuration | Changing | Change the configurations of an instance | For more information, see Change process and impact. |
Adjust the number of shards for an ApsaraDB for Redis instance | Changes to the configurations of the instance may cause unstable latency. However, ApsaraDB for Redis supports scaling without leading to transient connections and the read-only state. 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 one or more ApsaraDB for Redis instances | A transient connection occurs on the instance. 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 |
|
Upgrading Minor Version | MinorVersionUpgrading | Update the minor version | |
Configuring Network | NetworkModifying | Change the network type from classic network to VPC |
|
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 for an ApsaraDB for Redis instance | None | ||
Release a public endpoint for an ApsaraDB for Redis instance | 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 private endpoint before you can perform the preceding operations. |
||
Release a private endpoint for an ApsaraDB for Redis instance | 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 | The instance restarts after you enable SSL encryption or update the certificate validity period. A transient connection occurs on the instance. 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 |
|
Restarting | Rebooting | Restart one or more ApsaraDB for Redis instances | A transient connection occurs on the instance. 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:
|
Deleting Expired Data | CleaningUpExpiredData | If you choose to delete expired data, take note of the following impacts:
|
|
Switching | HASwitching | Manually switch workloads from a master node to a replica node |
|
Disabled | Inactive | None | The instance expires and cannot provide database services. If you want to continue to use the instance, you must manually 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 database services. The instance is not displayed on 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 instances in the recycle bin. |