ltcluster service unpause

ltcluster service unpause — Instruct all ltclusterd instances in the replication cluster to resume failover operations

Description

This command can be run on any active node in the replication cluster to instruct all running ltclusterd instances to "unpause" (following a previous execution of ltcluster service pause) and resume normal failover/monitoring operation.

Note

It's important to wait a few seconds after restarting LightDB on any node before running ltcluster service pause, as the ltclusterd instance on the restarted node will take a second or two before it has updated its status.

Prerequisites

LightDB must be accessible on all nodes (using the conninfo string shown by ltcluster cluster show) from the node where ltcluster service pause is executed.

Execution

ltcluster service unpause can be executed on any active node in the replication cluster. A valid ltcluster.conf file is required. It will have no effect on nodes which are not already paused.

Example

$ ltcluster -f /etc/ltcluster.conf service unpause
NOTICE: node 1 (node1) unpaused
NOTICE: node 2 (node2) unpaused
NOTICE: node 3 (node3) unpaused

Options

--dry-run

Check if nodes are reachable but don't unpause ltclusterd.

Exit codes

One of the following exit codes will be emitted by ltcluster service unpause:

SUCCESS (0)

ltclusterd could be unpaused on all nodes.

ERR_LTCLUSTERD_PAUSE (26)

ltclusterd could not be unpaused on one or mode nodes.

See also

ltcluster service pause, ltcluster service status, pausing the ltclusterd service, ltcluster daemon start, ltcluster daemon stop