diff options
| author | Gabriel Mazetto <brodock@gmail.com> | 2019-07-31 17:44:33 +0200 |
|---|---|---|
| committer | Gabriel Mazetto <brodock@gmail.com> | 2019-08-05 00:08:24 +0200 |
| commit | 8552bbef4e59cba35d685da326de07512985b997 (patch) | |
| tree | be4b60ade812e0f391ecb8af55b89035b31fce98 | |
| parent | 8de4fc0aa4c75b0c1bec23595017b78302b34b93 (diff) | |
| download | gitlab-ce-brodock/fix-geo-upgrade-docs.tar.gz | |
Simplify general update stepsbrodock/fix-geo-upgrade-docs
| -rw-r--r-- | doc/administration/geo/replication/updating_the_geo_nodes.md | 32 |
1 files changed, 15 insertions, 17 deletions
diff --git a/doc/administration/geo/replication/updating_the_geo_nodes.md b/doc/administration/geo/replication/updating_the_geo_nodes.md index dfd50112daa..39174780e24 100644 --- a/doc/administration/geo/replication/updating_the_geo_nodes.md +++ b/doc/administration/geo/replication/updating_the_geo_nodes.md @@ -10,10 +10,23 @@ all you need to do is update GitLab itself: 1. Log into each node (**primary** and **secondary** nodes). 1. [Update GitLab][update]. -1. [Update tracking database on **secondary** node](#update-tracking-database-on-secondary-node) when - the tracking database is enabled. 1. [Test](#check-status-after-updating) **primary** and **secondary** nodes, and check version in each. +### Check status after updating + +Now that the update process is complete, you may want to check whether +everything is working correctly: + +1. Run the Geo raketask on all nodes, everything should be green: + + ```sh + sudo gitlab-rake gitlab:geo:check + ``` + +1. Check the **primary** node's Geo dashboard for any errors. +1. Test the data replication by pushing code to the **primary** node and see if it + is received by **secondary** nodes. + ## Upgrading to GitLab 12.1 By default, GitLab 12.1 will attempt to automatically upgrade the embedded PostgreSQL server to 10.7 from 9.6. Please see [the omnibus documentation](https://docs.gitlab.com/omnibus/settings/database.html#upgrading-a-geo-instance) for the recommended procedure. @@ -419,21 +432,6 @@ is prepended with the relevant node for better clarity: sudo gitlab-ctl start ``` -### Check status after updating - -Now that the update process is complete, you may want to check whether -everything is working correctly: - -1. Run the Geo raketask on all nodes, everything should be green: - - ```sh - sudo gitlab-rake gitlab:geo:check - ``` - -1. Check the **primary** node's Geo dashboard for any errors. -1. Test the data replication by pushing code to the **primary** node and see if it - is received by **secondary** nodes. - ### Update tracking database on **secondary** node After updating a **secondary** node, you might need to run migrations on |