Commit fc1c40eb authored by Harsh Chouraria's avatar Harsh Chouraria Committed by Kati Paizee

Docs: Remove arbitrary 1 week wait note for zero-downtime upgrades

parent 8f36e57e
...@@ -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).
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment