search for: ctdb_capability_recmast

Hi, I came across the 'CTDB_CAPABILITY_LMASTER=no' and 'CTDB_CAPABILITY_RECMASTER=no' options in my quest to salvage a rather poorly performing CTDB cluster over Ceph(fs). Unfortunately, the docs provide not enough information for a clustering noop like myself. Would there be any benefit to disabling those options for a branch office node on a high-latency WAN connection?...

...ctdb/nodes CTDB_NOTIFY_SCRIPT=/etc/ctdb/notify.sh CTDB_DBDIR=/var/lib/ctdb CTDB_DBDIR_PERSISTENT=/var/lib/ctdb/persistent CTDB_EVENT_SCRIPT_DIR=/etc/ctdb/events.d CTDB_SOCKET=/var/lib/ctdb/ctdb.socket CTDB_TRANSPORT="tcp" CTDB_MONITOR_FREE_MEMORY=100 CTDB_START_AS_DISABLED="yes" CTDB_CAPABILITY_RECMASTER=yes CTDB_CAPABILITY_LMASTER=yes NATGW_PUBLIC_IP= NATGW_PUBLIC_IFACE= NATGW_DEFAULT_GATEWAY= NATGW_PRIVATE_IFACE= NATGW_PRIVATE_NETWORK= NATGW_NODES=/etc/ctdb/natgw_nodes CTDB_LOGFILE=/var/log/ctdb/log.ctdb CTDB_DEBUGLEVEL=2 CTDB_OPTIONS=

...ctdb/nodes CTDB_NOTIFY_SCRIPT=/etc/ctdb/notify.sh CTDB_DBDIR=/var/lib/ctdb CTDB_DBDIR_PERSISTENT=/var/lib/ctdb/persistent CTDB_EVENT_SCRIPT_DIR=/etc/ctdb/events.d CTDB_SOCKET=/var/lib/ctdb/ctdb.socket CTDB_TRANSPORT="tcp" CTDB_MONITOR_FREE_MEMORY=100 CTDB_START_AS_DISABLED="yes" CTDB_CAPABILITY_RECMASTER=yes CTDB_CAPABILITY_LMASTER=yes NATGW_PUBLIC_IP= NATGW_PUBLIC_IFACE= NATGW_DEFAULT_GATEWAY= NATGW_PRIVATE_IFACE= NATGW_PRIVATE_NETWORK= NATGW_NODES=/etc/ctdb/natgw_nodes CTDB_LOGFILE=/var/log/messages CTDB_DEBUGLEVEL=2 CTDB_OPTIONS= */etc/ctdb/nodes* 192.168.12.30 192.168.12.34 */etc/ctdb/publi...

...debian ulimit -n 30000 CTDB_NODES=/etc/ctdb/nodes CTDB_NOTIFY_SCRIPT=/etc/ctdb/notify.sh CTDB_DBDIR=/var/lib/ctdb CTDB_DBDIR_PERSISTENT=/var/lib/ctdb/persistent CTDB_EVENT_SCRIPT_DIR=/etc/ctdb/events.d CTDB_SOCKET=/tmp/ctdb.socket CTDB_TRANSPORT="tcp" CTDB_START_AS_DISABLED="no" CTDB_CAPABILITY_RECMASTER=yes CTDB_CAPABILITY_LMASTER=yes CTDB_LOGFILE=/var/log/ctdb/log.ctdb CTDB_DEBUGLEVEL=ERR CTDB_SUPPRESS_COREFILE=no CTDB_SYSLOG=no CTDB_RUN_TIMEOUT_MONITOR=no CTDB_MAX_PERSISTENT_CHECK_ERRORS=0 root at smb-cluster-1:~# ctdb status Number of nodes:2 pnn:0 10.10.10.1 OK (THIS NODE) pnn:1 10.10...

...-state database -> state database directory CTDB_DEBUG_LOCKS database -> lock debug script CTDB_DEBUG_HUNG_SCRIPT event -> debug script CTDB_NOSETSCHED/--nosetsched legacy -> realtime scheduling CTDB_CAPABILITY_RECMASTER/--no-recmaster legacy -> recmaster capability CTDB_CAPABILITY_LMASTER/--no-lmaster legacy -> lmaster capability CTDB_START_AS_STOPPED/--start-as-stopped legacy -> start as stopped CTDB_START_AS_DISABLED/--start-as-disabled legacy -> start as disabled...

...-state database -> state database directory CTDB_DEBUG_LOCKS database -> lock debug script CTDB_DEBUG_HUNG_SCRIPT event -> debug script CTDB_NOSETSCHED/--nosetsched legacy -> realtime scheduling CTDB_CAPABILITY_RECMASTER/--no-recmaster legacy -> recmaster capability CTDB_CAPABILITY_LMASTER/--no-lmaster legacy -> lmaster capability CTDB_START_AS_STOPPED/--start-as-stopped legacy -> start as stopped CTDB_START_AS_DISABLED/--start-as-disabled legacy -> start as disabled...

...-state database -> state database directory CTDB_DEBUG_LOCKS database -> lock debug script CTDB_DEBUG_HUNG_SCRIPT event -> debug script CTDB_NOSETSCHED/--nosetsched legacy -> realtime scheduling CTDB_CAPABILITY_RECMASTER/--no-recmaster legacy -> recmaster capability CTDB_CAPABILITY_LMASTER/--no-lmaster legacy -> lmaster capability CTDB_START_AS_STOPPED/--start-as-stopped legacy -> start as stopped CTDB_START_AS_DISABLED/--start-as-disabled legacy -> start as disabled...

...-state database -> state database directory CTDB_DEBUG_LOCKS database -> lock debug script CTDB_DEBUG_HUNG_SCRIPT event -> debug script CTDB_NOSETSCHED/--nosetsched legacy -> realtime scheduling CTDB_CAPABILITY_RECMASTER/--no-recmaster legacy -> recmaster capability CTDB_CAPABILITY_LMASTER/--no-lmaster legacy -> lmaster capability CTDB_START_AS_STOPPED/--start-as-stopped legacy -> start as stopped CTDB_START_AS_DISABLED/--start-as-disabled legacy -> start as disabled...

...-state database -> state database directory CTDB_DEBUG_LOCKS database -> lock debug script CTDB_DEBUG_HUNG_SCRIPT event -> debug script CTDB_NOSETSCHED/--nosetsched legacy -> realtime scheduling CTDB_CAPABILITY_RECMASTER/--no-recmaster legacy -> recmaster capability CTDB_CAPABILITY_LMASTER/--no-lmaster legacy -> lmaster capability CTDB_START_AS_STOPPED/--start-as-stopped legacy -> start as stopped CTDB_START_AS_DISABLED/--start-as-disabled legacy -> start as disabled...

...-state database -> state database directory CTDB_DEBUG_LOCKS database -> lock debug script CTDB_DEBUG_HUNG_SCRIPT event -> debug script CTDB_NOSETSCHED/--nosetsched legacy -> realtime scheduling CTDB_CAPABILITY_RECMASTER/--no-recmaster legacy -> recmaster capability CTDB_CAPABILITY_LMASTER/--no-lmaster legacy -> lmaster capability CTDB_START_AS_STOPPED/--start-as-stopped legacy -> start as stopped CTDB_START_AS_DISABLED/--start-as-disabled legacy -> start as disabled...

...node to be fully participating # in the cluster and slow things down. # For that case, set both roles to "no" for the remote node on the remote site # but leave the roles default to "yes" on the primary nodes in the central # datacentre. ## Type: yesno ## Default: yes CTDB_CAPABILITY_RECMASTER=yes ## Description: LMASTER capability. # By default all nodes are capable of both being LMASTER for records and # also for taking the RECMASTER role and perform recovery. # These parameters can be used to disable these two roles on a node. # Note: If there are NO available nodes left in a cluste...