table of contents
CTDBD(1) | CTDB - clustered TDB database | CTDBD(1) |
NAME¶
ctdbd - The CTDB cluster daemonSYNOPSIS¶
ctdbd [OPTION...]
DESCRIPTION¶
ctdbd is the main CTDB daemon.Note that ctdbd is not usually invoked directly. It is invoked via ctdbd_wrapper(1) or via the initscript.
See ctdb(7) for an overview of CTDB.
GENERAL OPTIONS¶
-d, --debug=DEBUGLEVELSee the DEBUG LEVELS section in ctdb(7) for more information.
--dbdir=DIRECTORY
Defaults to /var/lib/ctdb.
--dbdir-persistent=DIRECTORY
Defaults to /var/lib/ctdb/persistent.
--dbdir-state=DIRECTORY
Defaults to /var/lib/ctdb/state.
--event-script-dir=DIRECTORY
Default is CTDB_BASE/events.d, so usually /etc/ctdb/events.d, which is part of the CTDB installation.
--listen=IPADDR
By default ctdbd will select the first address from the nodes list that in can bind to. See also --nlist.
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.
--logging=STRING
Valid values are:
file:FILENAME
syslog[:METHOD]
Under heavy loads syslog(3) can block if the syslog daemon processes messages too slowly. This can cause CTDB to block when logging.
If METHOD is specified then it specifies an extension that causes logging to be done in a non-blocking mode. Note that this may cause messages to be dropped. METHOD must be one of:
nonblocking
udp
udp-rfc5424
--max-persistent-check-errors=NUM
The default value is 0. Setting this to non-zero allows a node with unhealthy persistent databases to startup and join the cluster as long as there is another node with healthy persistent databases.
--nlist=FILENAME
Default is CTDB_BASE/nodes, so usually /etc/ctdb/nodes.
--no-lmaster
Please see the REMOTE CLUSTER NODES section in ctdb(7) for more information.
--no-recmaster
Please see the REMOTE CLUSTER NODES section in ctdb(7) for more information.
--notification-script=FILENAME
This file is usually /etc/ctdb/notify.sh.
Please see the NOTIFICATION SCRIPT section in ctdb(7) for more information.
--pidfile=FILENAME
The default is to not create a PID file.
--public_addresses=FILENAME
The IP addresses specified in this file can differ across nodes.
This is usually the file /etc/ctdb/public_addresses
--public-interface=INTERFACE
When using public IP addresses, this is only required if interfaces are not explicitly specified in the public addresses file.
--reclock=LOCK
For information about the recovery lock please see the RECOVERY LOCK section in ctdb(7).
--start-as-disabled
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.
--start-as-stopped
To allow the node to take part in the cluster it must be manually continued with the the ctdb enable command.
Please see the NODE STATES section in ctdb(7) for more information about the STOPPED state.
--transport=tcp|infiniband
The "infiniband" support is not regularly tested.
-?, --help
DEBUGGING OPTIONS¶
-i, --interactive--nopublicipcheck
--nosetsched
Normally ctdbd will change its scheduler to run as a real-time process. This is the default mode for a normal ctdbd operation to gurarantee that ctdbd always gets the CPU cycles that it needs.
This option is used to tell ctdbd to not run as a real-time process and instead run ctdbd as a normal userspace process. This is useful for debugging and when you want to run ctdbd under valgrind or gdb. (You don't want to attach valgrind or gdb to a real-time process.)
--socket=FILENAME
The default is /var/run/ctdb/ctdbd.socket. You only need to use this option if you plan to run multiple ctdbd daemons on the same physical host, usually for testing.
--script-log-level=DEBUGLEVEL
See the DEBUG LEVELS section in ctdb(7) for more information.
--sloppy-start
--torture
Do not use this option unless you are developing and testing new functionality in CTDB.
--valgrinding
SEE ALSO¶
ctdb(1), ctdbd_wrapper(1), onnode(1), ctdb(7), ctdb-tunables(7), http://ctdb.samba.org/AUTHOR¶
This documentation was written by Ronnie Sahlberg, Amitay Isaacs, Martin Schwenke
COPYRIGHT¶
Copyright © 2007 Andrew Tridgell, Ronnie SahlbergThis 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.
04/05/2019 | ctdb |