You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/en/upgrade/02_14_upgrade_to_17.md
+48-9Lines changed: 48 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,12 +19,6 @@ Versions 3.16 and 3.18 support GitLab versions that lag behind the official vers
19
19
20
20
## Process Overview
21
21
22
-
:::warning
23
-
The time required for the upgrade varies significantly depending on the size of the GitLab data. It may take several days to complete the upgrade, **so it's necessary to evaluate the maintenance window in advance**.
24
-
25
-
Test data: Includes 3 projects (one large project of 666MB, 2 empty projects), backup file size of 668MB, upgrade time of 8 hours.
26
-
:::
27
-
28
22
### Data Migration Path
29
23
30
24
According to the [official upgrade path](https://gitlab-com.gitlab.io/support/toolbox/upgrade-path/?current=14.0.12&target=17.8.1&distro=docker&edition=ce) documentation, the data migration path is as follows:
@@ -58,6 +52,28 @@ Back up the `platform-deployed` GitLab and restore it to an `all-in-one` image d
58
52
For the latest GitLab instance and operator versions, please refer to the [Release Note](../overview/release_notes.mdx).
59
53
:::
60
54
55
+
:::tip Migration Duration
56
+
The migration process involves database and repository backup/restore operations:
57
+
58
+
- Larger databases increase migration time.
59
+
- A higher number of repositories or larger single repositories significantly extends the duration.
60
+
- Storage performance also impacts efficiency — using topolvm is recommended for better performance.
61
+
62
+
Test setup:
63
+
64
+
- One large repository (~600 MB), others are small initial repositories
0 commit comments