Commit 2a05d42d authored by Fabian Zimmer's avatar Fabian Zimmer Committed by Achilleas Pipinellis

Removed the --force section

The section is out of place and makes no sense here.
parent 3027ba6f
......@@ -130,27 +130,19 @@ Note the following when promoting a secondary:
1. Promote the **secondary** node to the **primary** node.
Before promoting a secondary node to primary, preflight checks should be run. They can be run separately or along with the promotion script.
To promote the secondary node to primary along with preflight checks:
```shell
gitlab-ctl promote-to-primary-node
```
If you have already run the [preflight checks](planned_failover.md#preflight-checks) or don't want to run them, you can skip preflight checks with:
If you have already run the [preflight checks](planned_failover.md#preflight-checks) separately or don't want to run them, you can skip preflight checks with:
```shell
gitlab-ctl promote-to-primary-node --skip-preflight-check
```
You can also run preflight checks separately:
```shell
gitlab-ctl promotion-preflight-checks
```
After all the checks are run, you will be asked for a final confirmation before the promotion to primary. To skip this confirmation, run:
You can also promote the secondary node to primary **without any further confirmation**, even when preflight checks fail:
```shell
gitlab-ctl promote-to-primary-node --force
......
......@@ -51,12 +51,6 @@ Run this command to list out all preflight checks and automatically check if rep
gitlab-ctl promotion-preflight-checks
```
You can run this command in `force` mode to promote to primary even if preflight checks fail:
```shell
sudo gitlab-ctl promote-to-primary-node --force
```
Each step is described in more detail below.
### Object storage
......
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