You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: pages/managed-databases-for-redis/concepts.mdx
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,6 +20,8 @@ A Redis™<sup>*</sup> cluster consists of a set of primary and secondary nodes.
20
20
21
21
Each Managed Database for Redis™ cluster consists of minimum three and maximum six compute Instances hosting each a primary Redis™ Instance and a secondary Instance for one of the other nodes. If one of the primary nodes fails, the remaining nodes hold a vote and elect one of the remaining secondary nodes as the new primary node. When the failing node rejoins the cluster, it automatically becomes a secondary node and begins to replicate the data of another primary node.
22
22
23
+
Learn more about the cluster mode on the [Managed Databases for Redis™ FAQ page](/managed-databases-for-redis/faq/#what-is-the-logic-behind-the-cluster-mode).
24
+
23
25
## Endpoint
24
26
25
27
An endpoint is a point of connection to a database. The endpoint is associated with one or more public IPv4 addresses and a port, or with a private IPv4 and a port (if you use [Private Networks](/vpc/concepts/#private-networks)).
0 commit comments