diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-02-12 15:09:01 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-02-12 15:09:01 +0300 |
commit | bd497e352ebd279536ae11855871162e82a3f88c (patch) | |
tree | 2241444d4be33e199d7011b872713071a8f8cd41 /doc/administration/geo | |
parent | 0388886f9439fa93efea29a159522aec5643f7c8 (diff) |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/administration/geo')
-rw-r--r-- | doc/administration/geo/disaster_recovery/index.md | 19 |
1 files changed, 19 insertions, 0 deletions
diff --git a/doc/administration/geo/disaster_recovery/index.md b/doc/administration/geo/disaster_recovery/index.md index 2999e0b6f1d..5455e5914e1 100644 --- a/doc/administration/geo/disaster_recovery/index.md +++ b/doc/administration/geo/disaster_recovery/index.md @@ -205,6 +205,25 @@ secondary domain, like changing Git remotes and API URLs. This command will use the changed `external_url` configuration defined in `/etc/gitlab/gitlab.rb`. +1. For GitLab 11.11 through 12.7 only, you may need to update the primary + node's name in the database. This bug has been fixed in GitLab 12.8. + + To determine if you need to do this, search for the + `gitlab_rails["geo_node_name"]` setting in your `/etc/gitlab/gitlab.rb` + file. If it is commented out with `#` or not found at all, then you will + need to update the primary node's name in the database. You can search for it + like so: + + ```shell + grep "geo_node_name" /etc/gitlab/gitlab.rb + ``` + + To update the primary node's name in the database: + + ```shell + gitlab-rails runner 'Gitlab::Geo.primary_node.update!(name: GeoNode.current_node_name)' + ``` + 1. Verify you can connect to the newly promoted **primary** using its URL. If you updated the DNS records for the primary domain, these changes may not have yet propagated depending on the previous DNS records TTL. |