- bookworm 2:4.17.12+dfsg-0+deb12u1
- bookworm-backports 2:4.20.4+dfsg-1~bpo12+1
- testing 2:4.21.0~rc1+really4.20.4+dfsg-1
- unstable 2:4.21.0+dfsg-1
- experimental 2:4.21.0~rc2+dfsg-1
CTDB.CONF(5) | CTDB - clustered TDB database | CTDB.CONF(5) |
NAME¶
ctdb.conf - CTDB configuration file
DESCRIPTION¶
This file contains CTDB configuration options that affect the operation of CTDB daemons and command-line tools. The default location of this file is /etc/ctdb/ctdb.conf.
Note that this is a Samba-style configuration file, so it has a very different syntax to previous CTDB configuration files.
For event script options please see ctdb-script.options(5).
Configuration options are grouped into several sections below. There are only a few options in each section, allowing them to be ordered (approximately) in decreasing order of importance.
LOGGING CONFIGURATION¶
Options in this section control CTDB's logging. They are valid within the logging section of file, indicated by [logging].
log level = LOGLEVEL
Default: NOTICE
location = STRING
Valid values are:
file:FILENAME
syslog[:METHOD]
If METHOD is specified then it specifies an extension that causes logging to be done in a non-blocking fashion. This can be useful under heavy loads that might cause the syslog daemon to dequeue messages too slowly, which would otherwise cause CTDB to block when logging. METHOD must be one of:
nonblocking
udp
udp-rfc5424
Default: file:/var/log/ctdb/log.ctdb
CLUSTER CONFIGURATION¶
Options in this section affect the CTDB cluster setup. They are valid within the cluster section of file, indicated by [cluster].
cluster lock = LOCK
For information about the cluster lock please see the CLUSTER LOCK section in ctdb(7).
Default: NONE. However, uses of a cluster lock is strongly recommended.
leader capability = true|false
Please see the REMOTE CLUSTER NODES section in ctdb(7) for more information.
Default: true
leader timeout = SECONDS
Default: 5
node address = IPADDR
This option is only required when automatic address detection can not be used. This can be the case when running multiple ctdbd daemons/nodes on the same physical host (usually for testing), using InfiniBand for the private network or on Linux when sysctl net.ipv4.ip_nonlocal_bind=1.
Default: CTDB selects the first address from the nodes list that it can bind to. See also the PRIVATE ADDRESS section in ctdb(7).
transport = tcp|ib
ib means InfiniBand. The InfiniBand support is not regularly tested. If it is known to be broken then it may be disabled so that a value of ib is considered invalid.
Default: tcp
DATABASE CONFIGURATION¶
Options in this section affect the CTDB database setup. They are valid within the database section of file, indicated by [database].
volatile database directory = DIRECTORY
Mounting a tmpfs (or similar memory filesystem) on this directory can provide a significant performance improvement when there is I/O contention on the local disk.
Default: /var/lib/ctdb/volatile
persistent database directory=DIRECTORY
Default: /var/lib/ctdb/persistent
state database directory = DIRECTORY
Default: /var/lib/ctdb/state
tdb mutexes = true|false
If robust mutexes are unreliable on the platform being used then they can be disabled by setting this to false.
lock debug script = FILENAME
This script should be a bare filename relative to the CTDB configuration directory (/etc/ctdb/). Any directory prefix is ignored and the path is calculated relative to this directory.
CTDB provides a lock debugging script and installs it as /etc/ctdb/debug_locks.sh.
Default: NONE
EVENT HANDLING CONFIGURATION¶
Options in this section affect CTDB event handling. They are valid within the event section of file, indicated by [event].
debug script = FILENAME
This script should be a bare filename relative to the CTDB configuration directory (/etc/ctdb/). Any directory prefix is ignored and the path is calculated relative to this directory.
CTDB provides a script for debugging timed out event scripts and installs it as /etc/ctdb/debug-hung-script.sh.
Default: NONE
FAILOVER CONFIGURATION¶
Options in this section affect CTDB failover. They are valid within the failover section of file, indicated by [failover].
disabled = true|false
Default: false
LEGACY CONFIGURATION¶
Options in this section affect legacy CTDB setup. They are valid within the legacy section of file, indicated by [legacy].
ctdb start as stopped = true|false
To allow the node to take part in the cluster it must be manually continued with the ctdb continue command.
Please see the NODE STATES section in ctdb(7) for more information about the STOPPED state.
Default: false
start as disabled = true|false
To allow the node to host public IP addresses and services, it must be manually enabled using the ctdb enable command.
Please see the NODE STATES section in ctdb(7) for more information about the DISABLED state.
Default: false
realtime scheduling = true|false
Default: true
lmaster capability = true|false
Please see the REMOTE CLUSTER NODES section in ctdb(7) for more information.
Default: true
script log level = LOGLEVEL
See the DEBUG LEVELS section in ctdb(7) for more information.
Default: ERROR
FILES¶
SEE ALSO¶
ctdbd(1), onnode(1), ctdb.sysconfig(5), ctdb-script.options(5), ctdb(7), ctdb-tunables(7), http://ctdb.samba.org/
AUTHOR¶
This documentation was written by Amitay Isaacs, Martin Schwenke
COPYRIGHT¶
Copyright © 2007 Andrew Tridgell, Ronnie Sahlberg
This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 3 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with this program; if not, see http://www.gnu.org/licenses.
08/14/2024 | ctdb |