ApsaraDB for Redis allows you to change the configurations of instances. You can change the configurations such as the architecture and specifications of an instance to meet different performance and capacity requirements.
Billing
For more information, see Configuration change.
Change process and impacts
Instance | Change process and impact |
---|---|
|
![]()
|
|
During the configuration change, ApsaraDB for Redis migrates slots to the newly added data shards. This can help achieve imperceptible scaling. During this process, the latency remains under 100 milliseconds. |
Limits
Instance | Limits |
---|---|
Instances that use local disks |
|
Cluster instances that use cloud disks |
For more information, see Adjust the number of shards for an ApsaraDB for Redis instance. |
Child instance in a distributed instance |
|
When you downgrade the configurations of an instance, note that 90% of the memory capacity of the new instance is greater than the amount of occupied memory of the original instance. Otherwise, the instance cannot be downgraded. For example, assume that you have a performance-enhanced master-replica instance with 8 GB of memory and that 3 GB of the instance memory is occupied. You can change the instance into a performance-enhanced master-replica instance that has 4 GB of memory.
Manually change the configurations of an instance
Related API operations
Operation | Description |
---|---|
ModifyInstanceSpec | Changes the configurations of an ApsaraDB for Redis instance. |