From e4c76ca8cd41b3d37aa8eecfa29673247d86057c Mon Sep 17 00:00:00 2001 From: mich-elle-luna <153109578+mich-elle-luna@users.noreply.github.com> Date: Fri, 27 Sep 2024 14:42:14 -0700 Subject: [PATCH] add limitation to a-a doc #DOC-2229 add limitation to limitations section about UNLINK being blocking --- content/operate/rs/databases/active-active/planning.md | 1 + 1 file changed, 1 insertion(+) diff --git a/content/operate/rs/databases/active-active/planning.md b/content/operate/rs/databases/active-active/planning.md index f74f8f905c..ed033ddba2 100644 --- a/content/operate/rs/databases/active-active/planning.md +++ b/content/operate/rs/databases/active-active/planning.md @@ -83,6 +83,7 @@ Active-Active databases have the following limitations: - An existing database can't be changed into an Active-Active database. To move data from an existing database to an Active-Active database, you must [create a new Active-Active database]({{< relref "/operate/rs/databases/active-active/create.md" >}}) and [migrate the data]({{< relref "/operate/rs/databases/import-export/migrate-to-active-active.md" >}}). - [Discovery service]({{< relref "/operate/rs/databases/durability-ha/discovery-service.md" >}}) is not supported with Active-Active databases. Active-Active databases require FQDNs or [mDNS]({{< relref "/operate/rs/networking/mdns.md" >}}). - The `FLUSH` command is not supported from the CLI. To flush your database, use the API or Cluster Manager UI. +- The `UNLINK` command is a blocking command for all types of keys. - Cross slot multi commands (such as `MSET`) are not supported with Active-Active databases. - The hashing policy can't be changed after database creation. - If an Active-Active database [runs on flash memory]({{}}), you cannot add participating clusters that run on RAM only.