Commit 5271b02d authored by Nick Nguyen's avatar Nick Nguyen Committed by Achilleas Pipinellis

Clarify Patroni upgrade instructions

parent 78e66585
...@@ -1029,7 +1029,7 @@ Considering these, you should carefully plan your PostgreSQL upgrade: ...@@ -1029,7 +1029,7 @@ Considering these, you should carefully plan your PostgreSQL upgrade:
``` ```
NOTE: NOTE:
`gitlab-ctl pg-upgrade` tries to detect the role of the node. If for any reason the auto-detection does not work or you believe it did not detect the role correctly, you can use the `--leader` or `--replica` arguments to manually override it. On a Geo secondary site, the Patroni leader node is called `standby leader`.
1. Stop Patroni **only on replicas**. 1. Stop Patroni **only on replicas**.
...@@ -1049,6 +1049,11 @@ Considering these, you should carefully plan your PostgreSQL upgrade: ...@@ -1049,6 +1049,11 @@ Considering these, you should carefully plan your PostgreSQL upgrade:
sudo gitlab-ctl pg-upgrade -V 12 sudo gitlab-ctl pg-upgrade -V 12
``` ```
NOTE:
`gitlab-ctl pg-upgrade` tries to detect the role of the node. If for any reason the auto-detection
does not work or you believe it did not detect the role correctly, you can use the `--leader` or
`--replica` arguments to manually override it.
1. Check the status of the leader and cluster. You can proceed only if you have a healthy leader: 1. Check the status of the leader and cluster. You can proceed only if you have a healthy leader:
```shell ```shell
......
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