From fcae08f5a8349a2a703c06d670e4bb2a57b91ab6 Mon Sep 17 00:00:00 2001 From: Ian Barwick Date: Fri, 22 Sep 2017 15:27:17 +0900 Subject: [PATCH] Update README --- README.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index 5412be98..b1a9c02c 100644 --- a/README.md +++ b/README.md @@ -805,12 +805,12 @@ meaning replication changes "cascade" down through a hierarchy of servers. This can be used to reduce load on the primary and minimize bandwidth usage between sites. -`repmgr` supports cascading replication. When cloning a standby, in `repmgr.conf` -set the command-line parameter `--upstream-node-id` to the `node_id` of the -server the standby should connect to, and `repmgr` will perform the clone using -this server and create `recovery.conf` to point to it. Note that if `--upstream-node-id` -is not explicitly provided, `repmgr` will set the standby's `recovery.conf` to -point to the primary node. +`repmgr` supports cascading replication. When cloning a standby, set the +command-line parameter `--upstream-node-id` to the `node_id` of the +server the standby should connect to, and `repmgr` will create `recovery.conf` +pointing to this server. Note that if `--upstream-node-id` is not explicitly +provided, `repmgr` will set the standby's `recovery.conf` to point to the primary +node. To demonstrate cascading replication, ensure you have a primary and standby set up as shown above in the section "Setting up a simple replication cluster