Deprecated standalone instances

更新时间:
复制 MD 格式

ApsaraDB for Redis deprecated standalone instances on December 18, 2019 because they lack data persistence guarantees.

Deprecation reason

A standalone instance has only one master node. If the node fails, the system creates a data-empty node and switches workloads to it. You must then reload your application data. Because this failover can cause data loss, standalone instances are not suitable for scenarios that require data persistence and have been deprecated.

Deprecation date

Standalone instances have been deprecated since December 18, 2019.

Scope

All pay-as-you-go standalone instances (including Alibaba Gov Cloud and Alibaba Finance Cloud):

  • Standalone standard instances

  • Standalone cluster instances

Purchased standalone instances

Standalone instances that you already purchased continue to serve your workloads. However, they do not guarantee data persistence.

FAQ

During a failover, the HA system switches workloads to a data-empty node, which may cause data loss. Can I still use a standalone instance for cache-only scenarios?

If you accept the risk of data loss during a failover and only need the instance for non-persistent scenarios,you can create a pay-as-you-go standalone instance.