aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authormichaelbirnstiehl <michael.birnstiehl@sonarsource.com>2021-04-29 08:43:47 -0500
committersonartech <sonartech@sonarsource.com>2021-04-29 20:03:32 +0000
commitd62debd109bd54064ee87ab513886958b0e58b48 (patch)
treef56bae05016b0055b2632f027aa2b23b1aa440aa
parent1476a48fea64574ca131df89e31ccb62fee8a49d (diff)
downloadsonarqube-d62debd109bd54064ee87ab513886958b0e58b48.tar.gz
sonarqube-d62debd109bd54064ee87ab513886958b0e58b48.zip
SONAR-14759 Database schema upgrade can consume a lot of disk space
-rw-r--r--server/sonar-docs/src/pages/setup/upgrading.md3
1 files changed, 3 insertions, 0 deletions
diff --git a/server/sonar-docs/src/pages/setup/upgrading.md b/server/sonar-docs/src/pages/setup/upgrading.md
index 080b8045e64..9f3d4b465d1 100644
--- a/server/sonar-docs/src/pages/setup/upgrading.md
+++ b/server/sonar-docs/src/pages/setup/upgrading.md
@@ -36,6 +36,9 @@ This is a generic guide for upgrading across versions of SonarQube. Carefully re
[[warning]]
| Before you start, back up your SonarQube Database. Upgrade problems are rare, but you'll want the backup if anything does happen.
+### Database disk usage recommendations
+During your upgrade, tables may be duplicated to speed up the migration process, and this could cause your database disk usage to double. Because of this, we recommend that your database disk usage is below 50% before starting a migration.
+
### Upgrading from the ZIP file
1. Download and unzip the SonarQube distribution of your edition in a fresh directory, let's say `$NEW_SONAR_HOME`