Description
The FAILOVER command causes the backup node to take over all sets
that currently originate on the failed
node. slonik will contact all other
direct subscribers of the failed node to determine which node has
the highest sync status for each set. If another node has a
higher sync status than the backup node, the replication will
first be redirected so that the backup node replicates against
that other node, before assuming the origin role and allowing
update activity.
After successful failover, all former direct subscribers of the
failed node become direct subscribers of the backup node. The
failed node is abandoned, and can and should be removed from the
configuration with DROP NODE.
| Warning |
This command will abandon the status of the failed
node. There is no possibility to let the failed node join the
cluster again without rebuilding it from scratch as a slave. If
at all possible, you would likely prefer to use MOVE SET instead, as that does
not abandon the failed node.
|
- ID = ival
ID of the failed node
- BACKUP NODE = ival
Node ID of the node that will take over all
sets originating on the failed node
