Skip to content

Commit 5c2e0fd

Browse files
authored
docs: improve planning section with 2-node cluster guidance (patroni#3402)
- Add clarification about 2-node cluster behavior during failover - Emphasize DCS requirements (3 or 5 nodes) for proper consensus - Mention scaling capability: one DCS can handle thousands of Patroni clusters
1 parent 4a5cee7 commit 5c2e0fd

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

docs/README.rst

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -34,6 +34,10 @@ Patroni/PostgreSQL nodes are decoupled from DCS nodes (except when Patroni imple
3434
there is no requirement on the minimal number of nodes. Running a cluster consisting of one primary and one standby is
3535
perfectly fine. You can add more standby nodes later.
3636

37+
**2-node clusters** (primary + standby) are common and provide automatic failover with high availability. Note that during failover, you'll temporarily have no redundancy until the failed node rejoins.
38+
39+
**DCS requirements**: Your DCS (etcd, ZooKeeper, Consul) has to run with **3 or 5 nodes** for proper consensus and fault tolerance. A single DCS cluster can store information for hundreds or thousands of Patroni clusters using different namespace/scope combinations.
40+
3741
Running and Configuring
3842
-----------------------
3943

0 commit comments

Comments
 (0)