github/repmgr
1
0
Fork 0
mirror of https://github.com/EnterpriseDB/repmgr.git synced 2026-03-24 15:46:29 +00:00
Code Issues Packages Projects Releases 1 Wiki Activity

Use 100 as the default priority; 0 or less means node will never be promoted

Browse Source
This commit is contained in:
Ian Barwick
2015-03-26 10:38:20 +09:00
parent 15a531fed8
commit 3e621f43d1
7 changed files with 38 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
FAQ.md
View File

@@ -92,4 +92,22 @@ General
Not necessarily. However if you have an uneven number of nodes spread
over more than one network segment, a witness server will enable
better handling of a 'split brain' situation by providing a "casting
vote" on the preferred network segment.
vote" on the preferred network segment.
- How can I prevent a node from ever being promoted to master?
In `rempgr.conf`, set its priority to a value of 0 or less.
- Does `repmgrd` support delayed standbys?
`repmgrd` can monitor delayed standbys - those set up with
`recovery_min_apply_delay` set to a non-zero value in `recovery.conf` -
but as it's not currently possible to directly examine the value
applied to the standby, `repmgrd` may not be able to properly evaluate
the node as a promotion candidate.
We recommend that delayed standbys are explicitly excluded from promotion
by setting `priority` to 0 in `repmgr.conf`.
Note that after registering a delayed standby, `repmgrd` will only start
once the metadata added in the master node has been replicated.