Skip to content
Snippets Groups Projects

Docs for marking a batched BG migration finished

Merged Adam Hegyi requested to merge ah-marking-bg-migration-finished-doc into master
All threads resolved!
@@ -266,7 +266,7 @@ arguments until the status query returns no rows.
1. Run a reconfigure:
```plaintext
```plaintext
sudo gitlab-ctl reconfigure
```
@@ -327,9 +327,9 @@ sudo gitlab-rake gitlab:background_migrations:finalize[CopyColumnUsingBackground
#### Mark a batched migration finished
There can be cases where the background migration fails when jumping too many version upgrades or due to backward incompatible database
schema changes (example: [issue](https://gitlab.com/gitlab-org/gitlab/-/issues/393216)). Failed background migrations will prevent further
application upgrades.
There can be cases where the background migration fails: when jumping too many version upgrades,
or backward-incompatible database schema changes. (For an example, see [issue 393216](https://gitlab.com/gitlab-org/gitlab/-/issues/393216)).
Failed background migrations prevent further application upgrades.
When the background migration is determined to be "safe" to skip, the migration can be manually marked finished:
Loading