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
Lifecycle
Notice 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
Create an ApsaraDB for Redis instance ApsaraDB for Redis provides two editions: Community Edition and Enhanced Edition (Tair). ApsaraDB for Redis Enhanced Edition (Tair) has the following types of instance: Performance-enhanced instances, Persistent memory-optimized instances, and Storage-optimized instances. You can choose one based on your business requirements.
Change the configurations of an instance You can change the specifications, architecture, and type of your instance to meet the performance and compatibility requirements of different scenarios.
Adjust the number of shards for an ApsaraDB for Redis instance A larger number of shards result in higher instance performance. You can adjust the number of shards for an instance based on your business requirements. For more information about Community Edition with cloud disks, see Community Edition with cloud disks.
Restart one or more ApsaraDB for Redis instances If the number of connections reaches the upper limit or if performance issues occur, you can restart the ApsaraDB for Redis instance to close all connections.
Upgrade the major version You can upgrade the major version of an ApsaraDB for Redis instance, for example, from Redis 2.8 to Redis 4.0. After the major version of the instance is upgraded, you can use the features of the new version. For more information about new major versions, see the following topics:
Update 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 update the minor version of your instances at the earliest opportunity.
Release instances You can release idle pay-as-you-go instances to save resources.
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.