3.2 KiB
| stage | group | info | type |
|---|---|---|---|
| Enablement | Geo | To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers | howto |
Updating the Geo nodes (PREMIUM ONLY)
Updating Geo nodes involves performing:
- Version-specific update steps, depending on the version being updated to or from.
- 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.
- Updating to GitLab 12.9
- Updating to GitLab 12.7
- Updating to GitLab 12.2
- Updating to GitLab 12.1
- Updating to GitLab 12.0
- Updating to GitLab 11.11
- Updating to GitLab 10.8
- Updating to GitLab 10.6
- Updating to GitLab 10.5
- Updating to GitLab 10.3
- Updating to GitLab 10.2
- Updating to GitLab 10.1
- Updating to GitLab 10.0
- Updating from GitLab 9.3 or older
- Updating to GitLab 9.0
General update steps
NOTE: Note: These general update steps are not intended for high-availability deployments, and will cause downtime. If you want to avoid downtime, consider using zero downtime updates.
To update the Geo nodes when a new GitLab version is released, update primary and all secondary nodes:
- Log into the primary node.
- Update GitLab on the primary node using Omnibus.
- Log into each secondary node.
- Update GitLab on each secondary node using Omnibus.
- Test 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:
-
Run the Geo Rake task on all nodes, everything should be green:
sudo gitlab-rake gitlab:geo:check -
Check the primary node's Geo dashboard for any errors.
-
Test the data replication by pushing code to the primary node and see if it is received by secondary nodes.
If you encounter any issues, please consult the Geo troubleshooting guide.