diff options
Diffstat (limited to 'doc/update/index.md')
| -rw-r--r-- | doc/update/index.md | 47 |
1 files changed, 35 insertions, 12 deletions
diff --git a/doc/update/index.md b/doc/update/index.md index 98dfee04a41..3a17d3c01d7 100644 --- a/doc/update/index.md +++ b/doc/update/index.md @@ -85,7 +85,7 @@ Certain releases may require different migrations to be finished before you update to the newer version. [Batched migrations](#batched-background-migrations) are a migration type available in GitLab 14.0 and later. -Background migrations and batched migrations not the same, so you should check that both are +Background migrations and batched migrations are not the same, so you should check that both are complete before updating. Decrease the time required to complete these migrations by increasing the number of @@ -98,7 +98,7 @@ that can process jobs in the `background_migration` queue. ```shell sudo gitlab-rails runner -e production 'puts Gitlab::BackgroundMigration.remaining' -sudo gitlab-rails runner -e production 'puts Gitlab::BackgroundMigration.pending' +sudo gitlab-rails runner -e production 'puts Gitlab::Database::BackgroundMigrationJob.pending' ``` **For installations from source:** @@ -106,7 +106,7 @@ sudo gitlab-rails runner -e production 'puts Gitlab::BackgroundMigration.pending ```shell cd /home/git/gitlab sudo -u git -H bundle exec rails runner -e production 'puts Gitlab::BackgroundMigration.remaining' -sudo -u git -H bundle exec rails runner -e production 'puts Gitlab::BackgroundMigration.pending' +sudo -u git -H bundle exec rails runner -e production 'puts Gitlab::Database::BackgroundMigrationJob.pending' ``` ### Batched background migrations @@ -193,9 +193,9 @@ To address the above two scenario's, it is advised to do the following prior to 1. Wait until all jobs are finished. 1. Upgrade GitLab. -## Checking for pending Advanced Search migrations +## Checking for pending Advanced Search migrations **(PREMIUM SELF)** -This section is only applicable if you have enabled the [Elasticsearch integration](../integration/elasticsearch.md). +This section is only applicable if you have enabled the [Elasticsearch integration](../integration/elasticsearch.md) **(PREMIUM SELF)**. Major releases require all [Advanced Search migrations](../integration/elasticsearch.md#advanced-search-migrations) to be finished from the most recent minor release in your current version @@ -239,14 +239,12 @@ It is required to follow the following upgrade steps to ensure a successful *maj Identify a [supported upgrade path](#upgrade-paths). -It's also important to ensure that any background migrations have been fully completed -before upgrading to a new major version. To see the current size of the `background_migration` queue, -[Check for background migrations before upgrading](#checking-for-background-migrations-before-upgrading). +It's also important to ensure that any [background migrations have been fully completed](#checking-for-background-migrations-before-upgrading) +before upgrading to a new major version. -If you have enabled the [Elasticsearch integration](../integration/elasticsearch.md), then ensure -all Advanced Search migrations are completed in the last minor version within -your current version. Be sure to -[check for pending Advanced Search migrations](#checking-for-pending-advanced-search-migrations) +If you have enabled the [Elasticsearch integration](../integration/elasticsearch.md) **(PREMIUM SELF)**, then +[ensure all Advanced Search migrations are completed](#checking-for-pending-advanced-search-migrations) in the last minor version within +your current version before proceeding with the major version upgrade. If your GitLab instance has any runners associated with it, it is very @@ -539,6 +537,31 @@ See [Maintenance mode issue in GitLab 13.9 to 14.4](#maintenance-mode-issue-in-g - See [Maintenance mode issue in GitLab 13.9 to 14.4](#maintenance-mode-issue-in-gitlab-139-to-144). +- For GitLab Enterprise Edition customers, we noticed an issue when [subscription expiration is upcoming, and you create new subgroups and projects](https://gitlab.com/gitlab-org/gitlab/-/issues/322546). If you fall under that category and get 500 errors, you can work around this issue: + + 1. SSH into you GitLab server, and open a Rails console: + + ```shell + sudo gitlab-rails console + ``` + + 1. Disable the following features: + + ```ruby + Feature.disable(:subscribable_subscription_banner) + Feature.disable(:subscribable_license_banner) + ``` + + 1. Restart Puma or Unicorn: + + ```shell + #For installations using Puma + sudo gitlab-ctl restart puma + + #For installations using Unicorn + sudo gitlab-ctl restart unicorn + ``` + ### 13.8.8 GitLab 13.8 includes a background migration to address [an issue with duplicate service records](https://gitlab.com/gitlab-org/gitlab/-/issues/290008). If duplicate services are present, this background migration must complete before a unique index is applied to the services table, which was [introduced in GitLab 13.9](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/52563). Upgrades from GitLab 13.8 and earlier to later versions must include an intermediate upgrade to GitLab 13.8.8 and [must wait until the background migrations complete](#checking-for-background-migrations-before-upgrading) before proceeding. |