ApsaraDB for Redis instances with cloud disks are based on the new-generation control architecture of ApsaraDB for Redis. These instances allow you to adjust the number of shards and perform smooth scaling. In smooth scaling, transient connections do not occur and instances do not enter the read-only state. You can use these features to flexibly handle reads and writes on hot data and data skews.
Prerequisites
The instance is a persistent memory-optimized cluster instance. For more information about persistent memory-optimized instances and cluster instances, see Persistent memory-optimized instances and Cluster master-replica instances.
Precautions
- An instance can contain 1 to 32 shards.
- The operation cannot be scheduled to be performed in a maintenance window. After you adjust the number of shards, the instance immediately enters the Changing Configuration state and evenly distributes data on the shards.
- The duration of a configuration change is based on multiple factors such as the network conditions, task queue size, and data volume. A configuration change may cause a latency fluctuation. We recommend that you change configurations during off-peak hours. Make sure that your applications can automatically reconnect to instances.
Billing
For more information, see Configuration change.
Procedure
Related API operations
Operation | Description |
---|---|
AddShardingNode | Adds one or more shards to an ApsaraDB for Redis cluster instance. |
DeleteShardingNode | Deletes one or more shards from an ApsaraDB for Redis cluster instance. |