From f65efecac972a6ff2ef90c27f114b137d38e79d7 Mon Sep 17 00:00:00 2001 From: Michael Banck Date: Tue, 2 Aug 2022 10:14:37 +0200 Subject: [PATCH] Clarify standby cluster documentation. (#2369) This adds a paragraph to the Standby Cluster section clarifying that the standby cluster is independent of the primary cluster and not visible from the primary cluster's Patroni interface. Close #2090 --- docs/replica_bootstrap.rst | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/replica_bootstrap.rst b/docs/replica_bootstrap.rst index 1524f7f2..729e5d47 100644 --- a/docs/replica_bootstrap.rst +++ b/docs/replica_bootstrap.rst @@ -187,6 +187,13 @@ Standby leader holds and updates a leader lock in DCS. If the leader lock expires, cascade replicas will perform an election to choose another leader from the standbys. +There is no further relationship between the standby cluster and the primary +cluster it replicates from, in particular, they must not share the same DCS +scope if they use the same DCS. They do not know anything else from each other +apart from replication information. Also, the standby cluster is not being +displayed in ``patronictl list`` or ``patronictl topology`` output on the +primary cluster. + For the sake of flexibility, you can specify methods of creating a replica and recovery WAL records when a cluster is in the "standby mode" by providing `create_replica_methods` key in `standby_cluster` section. It is distinct from