From fd5dfa2ebcab8480c8ad7e00475f0f1f2a3e44a4 Mon Sep 17 00:00:00 2001 From: Ian Barwick Date: Tue, 8 Aug 2017 00:50:12 +0900 Subject: [PATCH] Document "archiver_lag_*" configuration settings. --- repmgr.conf.sample | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/repmgr.conf.sample b/repmgr.conf.sample index bd5801a5..8df195ab 100644 --- a/repmgr.conf.sample +++ b/repmgr.conf.sample @@ -245,6 +245,28 @@ ssh_options='-q' # Options to append to "ssh" #service_promote_command = '' # Note: this overrides any value contained # in the setting "promote_command" + +#------------------------------------------------------------------------------ +# Status check thresholds +#------------------------------------------------------------------------------ + +# Various warning/critical thresholds used by "repmgr node check". + +#archiver_lag_warning=16 # repmgr node check --archiver +#archiver_lag_critical=128 # + # Numbers of files pending archiving via PostgreSQL's + # "archive_command" configuration parameter. If + # files can't be archived fast enough, or the archive + # command is failing, the buildup of files can + # cause various issues, such as server shutdown being + # delayed until all files are archived, or excessive + # space being occupied by unarchived files. + # + # Note that these values will be checked when executing + # "repmgr standby switchover" to warn about potential + # issues with shutting down the demotion candidate. + + #------------------------------------------------------------------------------ # BDR monitoring options #------------------------------------------------------------------------------