Valery Sizov authored 4 years ago and Ian Baum committed 4 years ago

If replication was paused on secondary, we need to use the last point
in time for the database when we promote the node.

This is a proof-of-concept that adds a separate
configuration  for the GitLab cluster with the
more "high-level settings" for a Geo setup and
allows the Geo promotion task to alter these
settings.

It will allow promotion even if preflight checks
fail.

It will run preflight checks for promoting to
a primary node. `promote-to-primary-node` command
can include or optionally skip these checks.

This is a better way to promote a following database into primary

The promote-to-primary-node command is used for disaster recovery
using geo to recover quickly. It is possible the primary may never be
recovered, but at the very least it is almost certain that the primary
is not currently accessible.

This command should provide feedback that relates to the process of
making the GitLab instance accessible again. Additional data recovery
tasks, particularly those requiring the old primary to be brought back
online, are secondary and should be documented later in the process.