Skip to content

Commit 5bdf2b4

Browse files
Update active-active-redis.md
fix broken note
1 parent addfae0 commit 5bdf2b4

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

content/operate/rc/databases/configuration/active-active-redis.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -19,9 +19,9 @@ Active-Active databases allow read and write operations in each copy. Each copy
1919

2020
When developing for Active-Active databases, you need to consider some important differences. See [Develop applications with Active-Active databases]({{< relref "/operate/rs/databases/active-active/develop/_index.md" >}}) for related information.
2121

22-
{{< note >}}
22+
{{< note >}}
2323
Active-Active subscriptions on Redis Cloud are limited to a maximum of 10 regions and 10 databases.
24-
{{< /note >}}
24+
{{< /note >}}
2525

2626
## Active-Active geo-distributed replication highlights
2727

@@ -41,4 +41,4 @@ Active-Active databases use special data types called conflict-free data types (
4141

4242
After a failure at the process, node, or zone level, Active-Active databases automatically promote replica shards to replace failed primaries, copy data to new replica shards, and migrate shards to new nodes as needed. This reduces downtime and makes the most of your computing resources, even in the event of a failure.
4343

44-
Active-Active also provides a failover opportunity in case an entire cluster fails. Applications should redirect traffic to another cluster in the Active-Active deployment if a connected cluster fails. After the original cluster recovers, applications can direct traffic back to the original cluster. Redirecting traffic to alternate clusters is not handled automatically by Active-Active, so you must add redirection logic to the application. However, data automatically syncs to a recovered cluster when it returns to a healthy state.
44+
Active-Active also provides a failover opportunity in case an entire cluster fails. Applications should redirect traffic to another cluster in the Active-Active deployment if a connected cluster fails. After the original cluster recovers, applications can direct traffic back to the original cluster. Redirecting traffic to alternate clusters is not handled automatically by Active-Active, so you must add redirection logic to the application. However, data automatically syncs to a recovered cluster when it returns to a healthy state.

0 commit comments

Comments
 (0)