Standalone instances of ApsaraDB for Redis have been deprecated since December 18, 2019.
Deprecation reason
A standalone instance of ApsaraDB for Redis has only one master node. If the node fails, the system creates a new node that does not store any service data and switches the workloads to the new node. After the failover, you must load your application data to the new node. If a standalone instance is used in scenarios where data persistence is required, some data may be lost. To avoid data loss, standalone instances have been deprecated.
Deprecation date
Standalone instances have been deprecated since December 18, 2019.
Scope
All pay-as-you-go standalone instances :
- Standalone standard instances
- Standalone cluster instances
Purchased standalone instances
The standalone instances of ApsaraDB for Redis that you have purchased continue to serve your workloads. However, these instances are not suitable for scenarios where data persistence is required.
FAQ
If a standalone instance fails, a high-availability (HA) system switches the workloads to a new node that does not store any service data. Data loss may occur during the failover process. Can I use the standalone instance in cache-only scenarios?
If you know that data loss may occur on a standalone instance after the failover and you want to use the instance in scenarios where data persistence is not required, you can submit a ticket to activate the instance.