Manual Failover

In a DR configuration, a forced, manual failover is required in the event of a catastrophic/permanent leader node failure.

If the leader node is still accessible, fail over using the Settings > Cluster screen instead.

❗️

Important

Once a follower has been promoted this way, the old (failed) leader, if recoverable, should not be restarted until the seq node follow command has been run on it to set it back into the follower state.

If the old leader node is started without switching it into follower mode, data loss may occur.

1. Identify which node is to become the new leader

If the leader node catastrophically fails or is otherwise lost, the follower node can be promoted to become the new leader.

2. Promote the new leader

Windows: At an administrative shell prompt, promote the old follower to become the new leader by running:

seq node lead
seq service restart

Docker: In an init script run:

#!/bin/bash
seqsvr node lead

After the init script is run, the server process will start automatically.

👍

If, after reading these instructions you're unsure about how to recover your Seq instance, please reach out to [email protected] for help 🙂