Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
fc1c40eb
Commit
fc1c40eb
authored
Jul 22, 2021
by
Harsh Chouraria
Committed by
Kati Paizee
Jul 22, 2021
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Docs: Remove arbitrary 1 week wait note for zero-downtime upgrades
parent
8f36e57e
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
4 additions
and
3 deletions
+4
-3
doc/update/index.md
doc/update/index.md
+4
-3
No files found.
doc/update/index.md
View file @
fc1c40eb
...
@@ -273,9 +273,10 @@ migrating data. Background migrations are only added in the monthly releases.
...
@@ -273,9 +273,10 @@ migrating data. Background migrations are only added in the monthly releases.
Certain major/minor releases may require a set of background migrations to be
Certain major/minor releases may require a set of background migrations to be
finished. To guarantee this, such a release processes any remaining jobs
finished. To guarantee this, such a release processes any remaining jobs
before continuing the upgrading procedure. While this doesn't require downtime
before continuing the upgrading procedure. While this doesn't require downtime
(if the above conditions are met) we recommend users to keep at least 1 week
(if the above conditions are met) we require that you
[
wait for background
between upgrading major/minor releases, allowing the background migrations to
migrations to complete
](
#checking-for-background-migrations-before-upgrading
)
finish. The time necessary to complete these migrations can be reduced by
between each major/minor release upgrade.
The time necessary to complete these migrations can be reduced by
increasing the number of Sidekiq workers that can process jobs in the
increasing the number of Sidekiq workers that can process jobs in the
`background_migration`
queue. To see the size of this queue,
`background_migration`
queue. To see the size of this queue,
[
Check for background migrations before upgrading
](
#checking-for-background-migrations-before-upgrading
)
.
[
Check for background migrations before upgrading
](
#checking-for-background-migrations-before-upgrading
)
.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment