Chapter 11. ltclusterd setup and configuration

Table of Contents

11.1. ltclusterd configuration
11.1.1. Required configuration for automatic failover
11.1.2. Optional configuration for automatic failover
11.1.3. Configuring ltclusterd and pgbouncer to fence a failed primary node
11.1.4. LightDB service configuration
11.1.5. ltclusterd service configuration
11.1.6. Monitoring configuration
11.1.7. Applying configuration changes to ltclusterd
11.2. ltclusterd daemon
11.2.1. ltclusterd's PID file
11.2.2. ltclusterd daemon configuration on Debian/Ubuntu
11.3. ltclusterd connection settings
11.4. ltclusterd log rotation
11.5. Optional configuration for check LightDB

ltclusterd is a daemon process which runs on each LightDB node, monitoring the local node, and (unless it's the primary node) the upstream server (the primary server or with cascading replication, another standby) which it's connected to.

ltclusterd can be configured to provide failover capability in case the primary or upstream node becomes unreachable, and/or provide monitoring data to the ltcluster metadatabase.

From ltcluster 4.4, when running on the primary node, ltclusterd can also monitor standby disconnections/reconnections (see Monitoring standby disconnections on the primary).