Updating Geo nodes involves performing:
- Version-specific update steps, depending on the version being updated to or from.
- General update steps, for all updates.
To update the Geo nodes when a new GitLab version is released, update primary and all secondary nodes:
- Optional: Pause replication on each secondary node.
- Log into the primary node.
- Update GitLab on the primary node using Omnibus’s Geo-specific steps.
- Log into each secondary node.
- Update GitLab on each secondary node using Omnibus’s Geo-specific steps.
- If you paused replication in step 1, resume replication on each secondary
- Test primary and secondary nodes, and check version in each.
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, see the Geo troubleshooting guide.