Ian Barwick
e4f7dc8234
Add copyright notices
2017-09-08 13:27:39 +09:00
Ian Barwick
e0888c1f62
repmgrd: handle SIGHUP
2017-08-29 12:55:13 +09:00
Ian Barwick
10ef30096c
"node check": add server role check
2017-08-14 22:57:09 +09:00
Ian Barwick
8d7d83347a
repmgrd: add log line to indicate node recovery detected
2017-07-31 09:58:13 +09:00
Ian Barwick
7cf3b9b618
repmgrd: improve logging of BDR monitoring
...
Also always log information about event_notification command
2017-07-27 21:12:41 +09:00
Ian Barwick
4cf66c33db
repmgrd: more fixes to BDR recovery handling
2017-07-27 16:33:41 +09:00
Ian Barwick
fed6fba4ef
repmgrd: more fixes for BDR node recovery
2017-07-27 14:13:39 +09:00
Ian Barwick
dc24d62009
repmgrd: improve BDR recovery handling
2017-07-27 11:53:55 +09:00
Ian Barwick
eff26b496c
repmgrd: updates for BDR monitoring
2017-07-27 09:49:53 +09:00
Ian Barwick
d3c2a0f505
repmgrd: record bdr_recovery event on the node which was up
...
Attempting to write on the recovered node may result in an
error if it hadn't already started up.
2017-07-24 18:56:18 +09:00
Ian Barwick
8f2dde3bde
repmgrd: log BDR node recovery on the running node, not the recovered node
...
The recovered node might still be starting up.
2017-07-24 12:50:51 +09:00
Ian Barwick
2c8dd49831
repmgrd: additional check to ensure only one node handles failover
...
It's possible the "failover" is completed by one repmgrd before the
other has a chance to react, in which case the am_bdr_failover_handler()
check will not apply. Instead check if the node record has already been
set to "inactive".
2017-07-17 16:47:42 +09:00
Ian Barwick
48a0aa3bf7
repmgrd: improve failover handling
...
Make retry frequency/interval configurable as per streaming replication.
2017-07-17 14:56:52 +09:00
Ian Barwick
0dcd479322
Store node status in node record struct
2017-07-17 13:50:17 +09:00
Ian Barwick
a29bc3e0fa
Rename config.[ch] to configfile.[ch]
2017-07-16 09:41:26 +09:00
Ian Barwick
b1051bfca2
Minor fixes to BDR code
2017-07-16 08:27:07 +09:00
Ian Barwick
c93eb10ad3
Handle node recovery
2017-07-14 16:15:10 +09:00
Ian Barwick
951c7dbd07
repmgrd: in BDR mode, have each repmgrd monitor each node
...
This will cover both the case when an entire node including
repmgrd goes down, and when one PostgreSQL instance goes down
but repmgrd is still up (in which case only one of the repmgrds
will handle the failover).
2017-07-14 15:01:18 +09:00
Ian Barwick
e3b3fb65f0
repmgrd: restrict BDR monitoring to two node setup
...
It's not safe to have more than two nodes with this kind of
"failover", so we don't need to select alternative nodes by
priority.
2017-07-14 12:56:11 +09:00
Ian Barwick
dfcf85a62f
repmgrd: further BDR sanity checks
2017-07-14 10:27:28 +09:00
Ian Barwick
875cdf5102
repmgrd: don't run in BDR mode on a node marked as inactive
2017-07-14 09:59:56 +09:00
Ian Barwick
aeba2e31f1
repmgrd: fix BDR sanity check
2017-07-14 09:54:34 +09:00
Ian Barwick
d77e8d4d22
repmgrd: split physical and BDR functionality into separate files
2017-07-13 17:21:29 +09:00
