summaryrefslogtreecommitdiff
path: root/doc/development/background_migrations.md
diff options
context:
space:
mode:
authorBob Van Landuyt <bob@vanlanduyt.co>2018-02-08 09:15:45 +0100
committerBob Van Landuyt <bob@vanlanduyt.co>2018-02-08 09:44:59 +0100
commit917fb1744c10cdddd50c22bda690dfcca9a47eff (patch)
tree7e7aa527a9a2f2e0cdd3594ffbb1b5c4af994f9b /doc/development/background_migrations.md
parent0478ff7cd44d291e931436b8fcd4c5c53b249741 (diff)
downloadgitlab-ce-917fb1744c10cdddd50c22bda690dfcca9a47eff.tar.gz
[docs] Info rescheduling background migrationsbvl-fix-concurrent-fork-network-migrations
Diffstat (limited to 'doc/development/background_migrations.md')
-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:**