2.3 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/#assignments | howto |
Updating the Geo sites (PREMIUM SELF)
WARNING: Read these sections carefully before updating your Geo sites. Not following version-specific update steps may result in unexpected downtime. If you have any specific questions, contact Support.
Updating Geo sites involves performing:
- Version-specific update steps, depending on the version being updated to or from.
- General update steps, for all updates.
General update steps
NOTE: These general update steps are not intended for multi-site deployments, and will cause downtime. If you want to avoid downtime, consider using zero downtime upgrades.
To update the Geo sites when a new GitLab version is released, update primary and all secondary sites:
- Optional: Pause replication on each secondary sites.
- SSH into each node of the primary site.
- Upgrade GitLab on the primary site.
- SSH into each node of secondary sites.
- Upgrade GitLab on each secondary site.
- If you paused replication in step 1, resume replication on each secondary
- Test primary and secondary sites, 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 an application node for the primary and secondary sites. Everything should be green:
sudo gitlab-rake gitlab:geo:check -
Check the primary site's Geo dashboard for any errors.
-
Test the data replication by pushing code to the primary site and see if it is received by secondary sites.
If you encounter any issues, see the Geo troubleshooting guide.