diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-10-25 15:07:15 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-10-25 15:07:15 +0300 |
| commit | df65129ab40540728d4b391fc1a21d5a1de87b9c (patch) | |
| tree | 70537d61226dcb2b330e76cbdf2b3c6f77fd6c62 /doc/administration | |
| parent | ef62043981093451b8ad3113d57c227251646f9f (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/administration')
| -rw-r--r-- | doc/administration/geo/disaster_recovery/index.md | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/doc/administration/geo/disaster_recovery/index.md b/doc/administration/geo/disaster_recovery/index.md index d6f6211ed4c..2f636dc6ba4 100644 --- a/doc/administration/geo/disaster_recovery/index.md +++ b/doc/administration/geo/disaster_recovery/index.md @@ -88,6 +88,7 @@ Note the following when promoting a secondary: - If you encounter an `ActiveRecord::RecordInvalid: Validation failed: Name has already been taken` error message during this process, for more information, see this [troubleshooting advice](../replication/troubleshooting.md#fixing-errors-during-a-failover-or-when-promoting-a-secondary-to-a-primary-site). +- You should [point the primary domain DNS at the newly promoted site](#step-4-optional-updating-the-primary-domain-dns-record). Otherwise, runners must be registered again with the newly promoted site, and all Git remotes, bookmarks, and external integrations must be updated. #### Promoting a **secondary** site running on a single node running GitLab 14.5 and later |