diff options
Diffstat (limited to 'doc/update/zero_downtime.md')
| -rw-r--r-- | doc/update/zero_downtime.md | 17 |
1 files changed, 13 insertions, 4 deletions
diff --git a/doc/update/zero_downtime.md b/doc/update/zero_downtime.md index bb5cd195e5d..0eb7a520850 100644 --- a/doc/update/zero_downtime.md +++ b/doc/update/zero_downtime.md @@ -93,8 +93,8 @@ meet the other online upgrade requirements mentioned above. ## Multi-node / HA deployment WARNING: -You can only upgrade one minor release at a time. So from 13.6 to 13.7, not to 13.8. -If you attempt more than one minor release, the upgrade may fail. +You can only upgrade one minor release at a time. So from 15.6 to 15.7, not to 15.8. +If you attempt more than one minor release, the upgrade may fail. ### Use a load balancer in front of web (Puma) nodes @@ -116,7 +116,7 @@ continue to accept connections but mark their respective health check endpoints to be unhealthy. On seeing this, the load balancer should disconnect them gracefully. -Puma restarts only after completing all the currently processing requests. +Puma restarts only after completing all the currently-processing requests. This ensures data and service integrity. Once they have restarted, the health check end points are marked healthy. @@ -180,6 +180,9 @@ Before you update the main GitLab application you must (in order): 1. Upgrade the Gitaly nodes that reside on separate servers. 1. Upgrade Praefect if using Gitaly Cluster. +Because of a [known issue](https://gitlab.com/groups/gitlab-org/-/epics/10328), Gitaly and Gitaly Cluster upgrades +cause some downtime. + #### Upgrade Gitaly nodes [Upgrade the GitLab package](package/index.md#upgrade-to-a-specific-version-using-the-official-repositories) on the Gitaly nodes one at a time to ensure access to Git repositories is maintained. @@ -465,6 +468,9 @@ Log in to your **primary** node, executing the following: sudo SKIP_POST_DEPLOYMENT_MIGRATIONS=true gitlab-rake db:migrate ``` +1. Copy the `/etc/gitlab/gitlab-secrets.json` file from the primary site to the secondary site if they're different. + The file must be the same on all of a site's nodes. + ### Update the Geo secondary site On each **secondary** node, executing the following: @@ -538,7 +544,7 @@ setting `gitlab_rails['auto_migrate'] = false` in ## Multi-node / HA deployment with Geo **(PREMIUM SELF)** WARNING: -You can only upgrade one minor release at a time. +You can only upgrade one minor release at a time. You also must first start with the Gitaly cluster, updating Gitaly one node one at a time. This will ensure access to the Git repositories for the remainder of the upgrade process. This section describes the steps required to upgrade a multi-node / HA deployment with Geo. Some steps must be performed on a particular node. This @@ -665,6 +671,9 @@ sudo gitlab-ctl hup puma sudo gitlab-ctl restart sidekiq ``` +1. Copy the `/etc/gitlab/gitlab-secrets.json` file from the primary site to the secondary site if they're different. The + file must be the same on all of a site's nodes. + ### Step 3: Update each Geo secondary multi-node deployment Only proceed if you have successfully completed all steps on the Geo **primary** multi-node deployment. |