Commit 13b50be1 authored by Nick Nguyen's avatar Nick Nguyen Committed by Amy Qualls

Add PgBouncer note to node demotion instructions

parent c485ec58
...@@ -45,9 +45,12 @@ To bring the former **primary** node up to date: ...@@ -45,9 +45,12 @@ To bring the former **primary** node up to date:
all the writes to this node](planned_failover.md#prevent-updates-to-the-primary-node) all the writes to this node](planned_failover.md#prevent-updates-to-the-primary-node)
during this procedure. during this procedure.
1. [Setup database replication](../setup/database.md). Note that in this 1. [Set up database replication](../setup/database.md). In this case, the **secondary** node
case, **primary** node refers to the current **primary** node, and **secondary** node refers to the refers to the former **primary** node.
former **primary** node. 1. If [PgBouncer](../../postgresql/pgbouncer.md) was enabled on the **current secondary** node
(when it was a primary node) disable it by editing `/etc/gitlab/gitlab.rb`
and running `sudo gitlab-ctl reconfigure`.
1. You can then set up database replication on the **secondary** node.
If you have lost your original **primary** node, follow the If you have lost your original **primary** node, follow the
[setup instructions](../setup/index.md) to set up a new **secondary** node. [setup instructions](../setup/index.md) to set up a new **secondary** node.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment