summaryrefslogtreecommitdiff
path: root/doc/development
diff options
context:
space:
mode:
authorYorick Peterse <yorickpeterse@gmail.com>2018-02-08 11:22:04 +0000
committerYorick Peterse <yorickpeterse@gmail.com>2018-02-08 11:22:04 +0000
commit07e1bcc0768d74b85135a2dff1d7cd3afd13f6de (patch)
tree0619790b5373fb38d84cb56edb9e4137e1679dd2 /doc/development
parent297b075bd7d3f6a2703ee8dd6c30ac05400e31a3 (diff)
parent917fb1744c10cdddd50c22bda690dfcca9a47eff (diff)
downloadgitlab-ce-07e1bcc0768d74b85135a2dff1d7cd3afd13f6de.tar.gz
Merge branch 'bvl-fix-concurrent-fork-network-migrations' into 'master'42861-include-external-files-in-gitlab-ci-yml-move-from-eep-to-ce
Fix concurrent fork network migrations Closes #41487 See merge request gitlab-org/gitlab-ce!16988
Diffstat (limited to 'doc/development')
-rw-r--r--doc/development/background_migrations.md12
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/development/background_migrations.md b/doc/development/background_migrations.md
index af2026c483e..fc1b202b5eb 100644
--- a/doc/development/background_migrations.md
+++ b/doc/development/background_migrations.md
@@ -94,6 +94,18 @@ jobs = [['BackgroundMigrationClassName', [1]],
BackgroundMigrationWorker.bulk_perform_in(5.minutes, jobs)
```
+### Rescheduling background migrations
+
+If one of the background migrations contains a bug that is fixed in a patch
+release, the background migration needs to be rescheduled so the migration would
+be repeated on systems that already performed the initial migration.
+
+When you reschedule the background migration, make sure to turn the original
+scheduling into a no-op by clearing up the `#up` and `#down` methods of the
+migration performing the scheduling. Otherwise the background migration would be
+scheduled multiple times on systems that are upgrading multiple patch releases at
+once.
+
## Cleaning Up
>**Note:**