This topic describes the lifecycle of a Tair (Redis OSS-compatible) instance. The lifecycle starts from the time when the instance is created to the time when the instance is released or unsubscribed.
Lifecycle
Figure 2. Lifecycle 
If you perform specific operations on an instance, the state of the instance changes. This affects the instance in different ways. For example, the service may be interrupted for a few seconds. For more information, see Instance states and impacts.
Operation | Description |
Tair (Redis OSS-compatible) is available in two editions: Tair (Enterprise Edition) and Redis Open-Source Edition. Tair (Enterprise Edition) provides the following types of instances: DRAM-based instances, persistent memory-optimized instances, and ESSD/SSD-based instances. You can choose an instance based on your business requirements. | |
You can change the specifications, architecture, and type of your instance to meet the performance and compatibility requirements of different scenarios. | |
You can enable the read/write splitting feature for a cluster instance when the number of read requests to the cluster instance exceeds the node performance limit. After you enable read/write splitting for an instance, the instance can automatically identify read and write requests and forward requests to corresponding nodes. This allows the instance to support high-concurrency read and write operations. | |
A larger number of shards result in higher instance performance. You can adjust the number of shards for a cloud-native instance based on your business requirements. For more information about the specifications of cloud-native instances, see Specifications of Redis Open-Source Edition cloud-native instances. | |
After you enable automatic scale-up for an instance, the instance is automatically scaled up if the average memory usage of the instance reaches the specified threshold. This helps you quickly cope with business peaks, prevent memory overflow, and ensure online business stability. | |
If the number of connections to an instance reaches the upper limit or if performance issues occur, you can restart the instance to close all connections. | |
You can upgrade the major version of a Redis Open-Source Edition instance, for example, from 2.8 to 4.0. After the major version of the instance is upgraded, you can use the functions and features of the new version. For more information, see New features and compatibility changes of major versions of Redis Open-Source Edition. | |
Alibaba Cloud continuously optimizes the kernel of Tair (Redis OSS-compatible) to fix security vulnerabilities and improve service stability. We recommend that you periodically check and update the minor version of your instances. | |
You can release idle pay-as-you-go instances to reduce resource usage. | |
The recycle bin is used to store expired, overdue, and released instances. You can renew, recreate, or permanently delete instances in the recycle bin. |