diff options
| author | Jose Ivan Vargas <jvargas@gitlab.com> | 2018-02-12 12:48:31 -0600 |
|---|---|---|
| committer | Jose Ivan Vargas <jvargas@gitlab.com> | 2018-02-12 12:48:31 -0600 |
| commit | c833a09d9156e26851746250460ddd2f091e73cd (patch) | |
| tree | 01791c2a8461b53c797b3d5b91858f98b07eb477 /doc/development/background_migrations.md | |
| parent | 46ae03628de47d1bef2683a3a5fe4963b3df7d52 (diff) | |
| parent | 0a22ff267b2d3d787d3da44d927caac7bd442832 (diff) | |
| download | gitlab-ce-c833a09d9156e26851746250460ddd2f091e73cd.tar.gz | |
Merge branch 'master' into jivl-update-katex
Diffstat (limited to 'doc/development/background_migrations.md')
| -rw-r--r-- | doc/development/background_migrations.md | 12 |
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:** |