Skip to content
Snippets Groups Projects

Add Consul Upgrade Documentation

Merged Add Consul Upgrade Documentation
2906-update-consul-documentation into master
All threads resolved!
Merged Robert Marshall requested to merge 2906-update-consul-documentation into master
All threads resolved!
Compare
and
Show latest version
1 file
+ 1
− 1
Compare changes
  • Side-by-side
  • Inline
doc/administration/high_availability/consul.md
+ 1
− 1
@@ -112,7 +112,7 @@ Nodes running GitLab-bundled Consul should be:
NOTE: **NOTE:**
Running `curl http://127.0.0.1:8500/v1/health/state/critical` from any Consul node will identify existing health issues in the cluster. The command will return an empty array if the cluster is healthy.
Consul clusters communicate using the raft protocol and, if the current leader goes offline, this causes a leader election. A leader node must exist to facilitate synchronization across the cluster. If too many nodes go offline at the same time, the cluster will lose quorum and not elect a leader due to [broken consensus](https://www.consul.io/docs/internals/consensus.html).
Consul clusters communicate using the raft protocol. If the current leader goes offline, there needs to be a leader election. A leader node must exist to facilitate synchronization across the cluster. If too many nodes go offline at the same time, the cluster will lose quorum and not elect a leader due to [broken consensus](https://www.consul.io/docs/internals/consensus.html).
Consult the [troubleshooting section](#troubleshooting) if the cluster is not able to recover after the upgrade. The [outage recovery](#outage-recovery) may be of particular interest.