repmgrd: improve handling of "degraded monitoring"

In some cases, the monitored upstream may not be available for a while
(e.g. network split), in which case it makes sense to have repmgrd
keep running and trying to reconnect. Previously it would just keel
over and quit.
This commit is contained in:
Ian Barwick
2017-07-06 17:13:00 +09:00
parent 6b82ecbafc
commit 35df85e67d
5 changed files with 195 additions and 42 deletions

View File

@@ -83,6 +83,7 @@ typedef struct
int reconnect_interval;
int retry_promote_interval_secs;
bool monitoring_history;
int degraded_monitoring_timeout;
/* witness settings */
int witness_repl_nodes_sync_interval_secs;
@@ -124,7 +125,7 @@ typedef struct
/* standby clone settings */ \
false, "", "", "", "", { NULL, NULL }, \
/* repmgrd settings */ \
FAILOVER_MANUAL, DEFAULT_LOCATION, DEFAULT_PRIORITY, "", "", 2, 60, 6, 10, 300, false, \
FAILOVER_MANUAL, DEFAULT_LOCATION, DEFAULT_PRIORITY, "", "", 2, 60, 6, 10, 300, false, -1, \
/* witness settings */ \
30, \
/* service settings */ \