This topic describes the lifecycle of an ApsaraDB for Redis instance. The lifecycle starts from the time when the instance is created to the time when the instance is released or unsubscribed.

Lifecycle

Figure 1. Lifecycle management
Lifecycle management
Notice When you perform specific operations on an instance, the state of the instance changes. This impacts 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
Create an instance ApsaraDB for Redis provides two editions, Community Edition and Enhanced Edition (Tair). ApsaraDB for Redis Enhanced Edition (Tair) has two instance types: Performance-enhanced instances and Hybrid-storage instances. You can create an ApsaraDB for Redis instance based on your business requirements.
Change specifications You can also change the specifications, architecture, and instance type to meet the performance and compatibility requirements of different scenarios.
Restart an instance When the number of connections reaches the upper limit or if performance issues occur, you can close all connections by restarting the ApsaraDB for Redis instance.
Upgrade the major version Upgrade the major version of an ApsaraDB for Redis instance, for example, from Redis 2.8 to Redis 4.0. After the instance is upgraded, you can use the features of the new version. For more information about the new version, see:
Upgrade the minor version Alibaba Cloud continuously optimizes the kernel of ApsaraDB for Redis to fix security vulnerabilities and improve service stability. We recommend that you periodically check and upgrade the minor version of your instances at the earliest opportunity.
Release instances You can release idle pay-as-you-go instances anytime.
Manage instances in the recycle bin ApsaraDB for Redis provides a recycle bin to store expired, overdue, and released ApsaraDB for Redis instances. You can renew, recreate, or permanently delete instances in the recycle bin.