sin/samba-mirror
1
0
Fork 0
mirror of https://github.com/samba-team/samba.git synced 2025-01-12 09:18:10 +03:00
Code
a0a82f1b6a
samba-mirror/ctdb/config
History
Martin Schwenke b80967f5dc ctdb-scripts: Drop script configuration variable CTDB_MONITOR_SWAP_USAGE 
CTDB's system memory monitoring in 05.system.script monitors both main
memory and swap.  The swap monitoring was originally based on
the (possibly incorrect, see below) idea that swap space stacks on top
of main memory, so that when a system starts filling swap space then
this is supposed to be a good sign that the system is running out of
memory.  Additionally, performance on a Linux system tends to be
destroyed by the I/O associated with a lot of swapping to spinning
disks.

However, some platforms default to creating only 4GB of swap space
even when there is 128GB of main memory.  With such a small swap to
main memory ratio, memory pressure can force swap to be nearly full
even when a significant amount of main memory is still available and
the system is performing well.  This suggests that checking swap
utilisation might be less than useful in many circumstances.

So, remove the separate swap space checking and change the memory
check to cover the total of main memory and swap space.

Test function set_mem_usage() still takes an argument for each of main
memory and swap space utilisation.  For simplicity, the same number is
now passed twice to make the intended results comprehensible.  This
could be changed later.

A couple of tests are cleaned up to no longer use hard-coded
/proc/meminfo and ps output.

Signed-off-by: Martin Schwenke <martin@meltin.net>
Reviewed-by: Amitay Isaacs <amitay@gmail.com>
2019-05-07 05:45:34 +00:00
..
events ctdb-scripts: Drop script configuration variable CTDB_MONITOR_SWAP_USAGE 2019-05-07 05:45:34 +00:00
nfs-checks.d ctdb-scripts: Stop/start mount/rquotad/status via NFS call-out 2019-03-31 10:45:20 +00:00
ctdb-crash-cleanup.sh ctdb-scripts: Use load_script_options() in miscellaneous scripts 2018-05-12 06:11:17 +02:00
ctdb.conf ctdb-config: Change example recovery lock setting to one that fails 2019-02-25 02:12:16 +01:00
ctdb.init ctdb-scripts: Split CTDB configuration loading 2018-03-28 02:57:20 +02:00
ctdb.service ctdb-config: Add default ctdb.sysconfig file, update ctdb.service 2018-05-12 06:11:17 +02:00
ctdb.sudoers ctdb-scripts: Update important installed files to use build-time defaults 2015-09-15 08:56:21 +02:00
ctdb.sysconfig ctdb-config: Add default ctdb.sysconfig file, update ctdb.service 2018-05-12 06:11:17 +02:00
ctdb.tunables ctdb-scripts: Tunables are now loaded from ctdb.tunables 2018-03-28 02:57:21 +02:00
ctdbd_wrapper ctdb: Drop configuration file ctdbd.conf 2018-05-17 07:03:04 +02:00
debug_locks.sh ctdb-scripts: Provide a gstack function if gstack is not available 2018-07-11 14:47:21 +02:00
debug-hung-script.sh ctdb-scripts: Use load_script_options() in miscellaneous scripts 2018-05-12 06:11:17 +02:00
functions ctdb-scripts: Allow load_system_config() to take multiple alternatives 2019-03-31 10:45:20 +00:00
nfs-linux-kernel-callout Revert "ctdb-scripts: Do not "correct" number of nfsd threads when it is 0" 2019-04-12 07:11:30 +00:00
notification.README ctdb-scripts: Change directory for notifications to events/notification 2018-06-05 17:47:26 +02:00
notify.sh ctdb-scripts: Change directory for notifications to events/notification 2018-06-05 17:47:26 +02:00
README ctdb-scripts: Move event scripts to events/legacy/ directory 2018-06-05 17:47:26 +02:00
script.options ctdb-scripts: Drop event script CTDB_MANAGED_<service> variables 2018-07-11 11:48:39 +02:00
statd-callout ctdb-scripts: Update statd-callout to try several configuration files 2019-03-31 10:45:20 +00:00

README 

This directory contains run-time support scripts for CTDB.

Selected highlights:

  ctdb.init

    An initscript for starting ctdbd at boot time.

  events/

    Eventscripts.  See events/README for more details.

  functions

    Support functions, sourced by eventscripts and other scripts.

  statd-callout

    rpc.statd high-availability callout to support lock migration on
    failover.

Notes:

* All of these scripts are written in POSIX Bourne shell.  Please
  avoid bash-isms, including the use of "local" variables (which are
  not available in POSIX shell).

* Do not use absolute paths for commands.  Unit tests attempt to
  replace many commands with stubs and can not do this if commands are
  specified with absolute paths.  The functions file controls $PATH so
  absolute paths should not be required.