kotovalexarian-likes-gitlab/gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity
gitlab-org--gitlab-foss/doc/administration/geo/replication/updating_the_geo_nodes.md

58 lines
2.9 KiB
Markdown
Raw Normal View History

Changing badges to use parentheses not brackets Previously, we used brackets to denote the tier badges, but this made Kramdown, the docs site Markdown renderer, show many warnings when building the site. This is now fixed by using parentheses instead of square brackets. This was caused by [PREMIUM] looking like a link to Kramdown, which couldn't find a URL there. See: - https://gitlab.com/gitlab-com/gitlab-docs/merge_requests/484 - https://gitlab.com/gitlab-org/gitlab-ce/issues/63800
2019-07-08 04:50:38 -04:00
# Updating the Geo nodes **(PREMIUM ONLY)**
Docs: Merge EE doc/​administration/​geo to CE
2019-05-05 12:08:21 -04:00
Separate doc for version specific Geo update steps To emphasize the happy path for updating Geo nodes, put the version specific steps in a separate document and cross-link them for discoverability. Closes https://gitlab.com/gitlab-org/gitlab-ee/issues/11881
2019-09-05 00:02:06 -04:00
Updating Geo nodes involves performing:
1. [Version-specific update steps](#version-specific-update-steps), depending on the
version being updated to or from.
1. [General update steps](#general-update-steps), for all updates.
## Version specific update steps
Depending on which version of Geo you are updating to/from, there may be
different steps.
Add latest changes from gitlab-org/gitlab@master
2020-02-12 10:09:37 -05:00
- [Updating to GitLab 12.7](version_specific_updates.md#updating-to-gitlab-127)
- [Updating to GitLab 12.2](version_specific_updates.md#updating-to-gitlab-122)
Separate doc for version specific Geo update steps To emphasize the happy path for updating Geo nodes, put the version specific steps in a separate document and cross-link them for discoverability. Closes https://gitlab.com/gitlab-org/gitlab-ee/issues/11881
2019-09-05 00:02:06 -04:00
- [Updating to GitLab 12.1](version_specific_updates.md#updating-to-gitlab-121)
Add latest changes from gitlab-org/gitlab@master
2020-03-03 19:07:52 -05:00
- [Updating to GitLab 12.0](version_specific_updates.md#updating-to-gitlab-120)
- [Updating to GitLab 11.11](version_specific_updates.md#updating-to-gitlab-1111)
Separate doc for version specific Geo update steps To emphasize the happy path for updating Geo nodes, put the version specific steps in a separate document and cross-link them for discoverability. Closes https://gitlab.com/gitlab-org/gitlab-ee/issues/11881
2019-09-05 00:02:06 -04:00
- [Updating to GitLab 10.8](version_specific_updates.md#updating-to-gitlab-108)
- [Updating to GitLab 10.6](version_specific_updates.md#updating-to-gitlab-106)
- [Updating to GitLab 10.5](version_specific_updates.md#updating-to-gitlab-105)
- [Updating to GitLab 10.3](version_specific_updates.md#updating-to-gitlab-103)
- [Updating to GitLab 10.2](version_specific_updates.md#updating-to-gitlab-102)
- [Updating to GitLab 10.1](version_specific_updates.md#updating-to-gitlab-101)
- [Updating to GitLab 10.0](version_specific_updates.md#updating-to-gitlab-100)
- [Updating from GitLab 9.3 or older](version_specific_updates.md#updating-from-gitlab-93-or-older)
- [Updating to GitLab 9.0](version_specific_updates.md#updating-to-gitlab-90)
Docs: Merge EE doc/​administration/​geo to CE
2019-05-05 12:08:21 -04:00
## General update steps
Changed Geo general update steps
2019-09-02 02:38:45 -04:00
NOTE: **Note:** These general update steps are not intended for [high-availability deployments](https://docs.gitlab.com/omnibus/update/README.html#multi-node--ha-deployment), and will cause downtime. If you want to avoid downtime, consider using [zero downtime updates](https://docs.gitlab.com/omnibus/update/README.html#zero-downtime-updates).
Docs: Merge EE doc/​administration/​geo to CE
2019-05-05 12:08:21 -04:00
Fix space in geo doc
2019-09-02 04:16:27 -04:00
To update the Geo nodes when a new GitLab version is released, update **primary**
Changed Geo general update steps
2019-09-02 02:38:45 -04:00
and all **secondary** nodes:
1. Log into the **primary** node.
1. [Update GitLab on the **primary** node using Omnibus](https://docs.gitlab.com/omnibus/update/README.html).
1. Log into each **secondary** node.
1. [Update GitLab on each **secondary** node using Omnibus](https://docs.gitlab.com/omnibus/update/README.html).
Docs: Merge EE doc/​administration/​geo to CE
2019-05-05 12:08:21 -04:00
1. [Test](#check-status-after-updating) **primary** and **secondary** nodes, and check version in each.
Geo: Some update instructions should be for 9.0.x only
2019-08-05 02:45:43 -04:00
### 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:
Add latest changes from gitlab-org/gitlab@master
2020-01-30 10:09:15 -05:00
```shell
Geo: Some update instructions should be for 9.0.x only
2019-08-05 02:45:43 -04:00
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.
Added cross reference to the troubleshooting guide
2019-09-01 22:48:55 -04:00
If you encounter any issues, please consult the [Geo troubleshooting guide](troubleshooting.md).
Copy permalink