Instance states, operations that trigger specific states, and impacts - Tair (Redis® OSS-Compatible)

This topic describes the different states of a Tair (Redis OSS-compatible) 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 impacts such as transient connections that last for a few seconds.

Instance states

You can use one of the following methods to obtain the state of an instance:

Use the console: You can view the state of an instance on the Instances page of the console.
Call an API operation: You can call the DescribeInstances operation to query the state of an instance.

State in the console	State in an API response	Operation that triggers the state	Description
Creating	Creating	Create an instance	After you create an instance, the instance enters this state. The instance cannot provide database services until it enters the Running state.
Running	Normal	N/A	The instance can provide database services in this state.
Converting	Transforming	Change the billing method to subscription Change the billing method to pay-as-you-go	No impact.
Changing Configuration	Changing	Change the configurations of an instance	For more information, see Change the configurations of an instance.
Changing Configuration	Changing	Adjust the number of shards for an instance	The change to instance configurations may cause unstable latency. However, Tair (Redis OSS-compatible) supports scaling without leading to transient connections or 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 an instance	Transient connections occur 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.
Upgrading Major Version	MajorVersionUpgrading	Upgrade the major version	See the corresponding documentation.
Updating Minor Version	MinorVersionUpgrading	Update the minor version of an instance	See the corresponding documentation.
Configuring Network	NetworkModifying	Switch the network type from classic network to VPC Change the VPC or vSwitch of an instance	After you switch the network type of an instance from classic network to VPC, you cannot switch it back to classic network. The instance may experience a transient connection of a few seconds. We recommend that you perform this operation during off-peak hours and make sure that your applications 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, the endpoint is released after the network type is switched. Then, clients cannot connect to the instance by using the classic network endpoint. In this case, you must change the database endpoint on your client at the earliest opportunity.
		Change the endpoint or port number of an 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 instance	No impact.
		Release a public endpoint for an 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	After you enable the direct connection mode for an instance, you cannot upgrade the major version of the instance or change the zone to which the instance belongs. If you want to upgrade the major version or change the zone, release the private endpoint first. For more information, see Upgrade the major version, Migrate an instance across zones, and Release a private endpoint for an instance.
		Release a private endpoint for an instance	Clients can no longer connect to the instance by using the original private endpoint. Update the connection information on the clients at the earliest opportunity.
Configuring SSL	SSLModifying	Enable TLS encryption	The instance restarts after you enable Transparent Layer Security (TLS) encryption or update the certificate validity period. Transient connections occur 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.
Modifying TDE	TEDModifying	Enable TDE	No impact.
Migrating to Another Zone	ZoneMigrating	Migrate an instance across zones	Transient connections occur 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. If you migrate an instance across zones, the virtual IP address (VIP) of the instance such as 172.16.88.60 is changed. However, the endpoint of the instance remains unchanged. We recommend that you connect to the instance by using the endpoint. If you use the VIP to connect to the instance, the connection fails. If the minor version of the instance is outdated, the system updates it to the latest version to ensure high performance and stability.
Flushing Instance	Flushing	Clear data	If you choose to delete all data, take note of the following impacts: The instance runs the FLUSHALL command to delete all data from the instance. The deleted data cannot be restored. This operation immediately deletes all data from the instance and can affect your online services. Proceed with caution. We recommend that you perform this operation during off-peak hours.
Deleting Expired Data	CleaningUpExpiredData	Clear data	If you choose to delete expired data, take note of the following impacts: The instance runs the SCAN command to delete all expired data from the instance. The deleted data cannot be restored. This operation immediately deletes all expired data from the instance and can affect your online services. Proceed with caution. We recommend that you perform this operation during off-peak hours.
Switching	HASwitching	Manually switch workloads from a master node to a replica node	The data nodes on which the switchover is performed are disconnected for a few seconds. A switchover has potential data loss risks. For example, the data may become inconsistent between the master and replica nodes due to synchronization latency. To prevent potential data loss risks caused by the switchover and data doublewrite caused by the Domain Name System (DNS) cache, the data nodes remain read-only for up to 30 seconds. After an instance enters the Switching state, you cannot manage this instance. For example, you cannot modify the instance configurations or migrate the instance to another zone.
Disabled	Inactive	N/A	The instance expires and cannot provide database services. If you want to continue using the instance, you must manually renew the instance. For more information, see Renewal.
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 is not 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 instances in the recycle bin.