debian-mirror-gitlab/doc/administration/geo/replication/updating_the_geo_nodes.md

53 lines
2.4 KiB
Markdown
Raw Normal View History

2020-06-23 00:09:42 +05:30
---
stage: Enablement
group: Geo
2021-02-22 17:27:13 +05:30
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
2020-06-23 00:09:42 +05:30
type: howto
---
2021-03-11 19:13:27 +05:30
# Updating the Geo nodes **(PREMIUM SELF)**
2019-07-31 22:56:46 +05:30
2021-02-22 17:27:13 +05:30
WARNING:
2021-01-29 00:20:46 +05:30
Read these sections carefully before updating your Geo nodes. Not following
version-specific update steps may result in unexpected downtime. If you have
any specific questions, [contact Support](https://about.gitlab.com/support/#contact-support).
2020-11-24 15:15:51 +05:30
2019-12-04 20:38:33 +05:30
Updating Geo nodes involves performing:
2020-11-24 15:15:51 +05:30
1. [Version-specific update steps](version_specific_updates.md), depending on the
2019-12-04 20:38:33 +05:30
version being updated to or from.
1. [General update steps](#general-update-steps), for all updates.
2019-07-31 22:56:46 +05:30
## General update steps
2021-02-22 17:27:13 +05:30
NOTE:
2020-07-28 23:09:34 +05:30
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).
2019-12-04 20:38:33 +05:30
To update the Geo nodes when a new GitLab version is released, update **primary**
and all **secondary** nodes:
2019-07-31 22:56:46 +05:30
2020-11-24 15:15:51 +05:30
1. **Optional:** [Pause replication on each **secondary** node.](../index.md#pausing-and-resuming-replication)
2019-12-04 20:38:33 +05:30
1. Log into the **primary** node.
2021-01-03 14:25:43 +05:30
1. [Update GitLab on the **primary** node using Omnibus's Geo-specific steps](https://docs.gitlab.com/omnibus/update/README.html#geo-deployment).
2019-12-04 20:38:33 +05:30
1. Log into each **secondary** node.
2021-01-03 14:25:43 +05:30
1. [Update GitLab on each **secondary** node using Omnibus's Geo-specific steps](https://docs.gitlab.com/omnibus/update/README.html#geo-deployment).
2020-11-24 15:15:51 +05:30
1. If you paused replication in step 1, [resume replication on each **secondary**](../index.md#pausing-and-resuming-replication)
2019-07-31 22:56:46 +05:30
1. [Test](#check-status-after-updating) **primary** and **secondary** nodes, and check version in each.
2019-10-12 21:52:04 +05:30
### Check status after updating
Now that the update process is complete, you may want to check whether
everything is working correctly:
2020-05-24 23:13:21 +05:30
1. Run the Geo Rake task on all nodes, everything should be green:
2019-10-12 21:52:04 +05:30
2020-03-13 15:44:24 +05:30
```shell
2019-10-12 21:52:04 +05:30
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.
2021-01-29 00:20:46 +05:30
If you encounter any issues, see the [Geo troubleshooting guide](troubleshooting.md).