summaryrefslogtreecommitdiff
path: root/doc/development/background_migrations.md
Commit message (Collapse)AuthorAgeFilesLines
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-07-231-5/+5
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-05-211-2/+2
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-04-211-8/+3
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-03-171-2/+3
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-02-191-5/+6
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-02-181-1/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-01-291-2/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-01-221-0/+7
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-12-171-5/+5
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-12-131-1/+6
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-09-241-1/+3
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-09-181-3/+3
|
* Standardised punctuation at end of sentencesRussell Dickenson2019-09-091-4/+4
|
* Removes regular migrations from background onesMayra Cabrera2019-09-041-6/+9
| | | | | Specifies that background migrations should be scheduled as post deployment migrations
* Update capitalization in /dev docsMarcel Amirault2019-08-271-1/+1
| | | | | Clean up capitalization in /development /gitlab-basics and /install
* Make unordered lists conform to styleguidedocs/fix-unordered-list-styleEvan Read2019-01-081-3/+3
| | | | - Also makes other minor Markdown fixes that were near the main fixes.
* Fix ActiveRecord::Migration deprecationsYorick Peterse2018-12-121-2/+2
| | | | | Extending from ActiveRecord::Migration is deprecated, but was still used in a bunch of places.
* Resolve "CE documentation is not CommonMark compliant"Brett Walker2018-09-061-20/+20
|
* Respond to DB health in background migrationsYorick Peterse2018-08-061-0/+3
| | | | | | | | | | | | | | | | | | | This changes the BackgroundMigration worker so it checks for the health of the DB before performing a background migration. This in turn allows us to reduce the minimum interval, without having to worry about blowing things up if we schedule too many migrations. In this setup, the BackgroundMigration worker will reschedule jobs as long as the database is considered to be in an unhealthy state. Once the database has recovered, the migration can be performed. To determine if the database is in a healthy state, we look at the replication lag of any replication slots defined on the primary. If the lag is deemed to great (100 MB by default) for too many slots, the migration is rescheduled for a later point in time. The health checking code is hidden behind a feature flag, allowing us to disable it if necessary.
* Add points regarding background migrations on huge tablesosw-background-migrations-best-practice-docOswaldo Ferreira2018-07-241-0/+8
|
* Fixed typosPascal Borreli2018-04-271-2/+2
|
* Add more detail to cleanup steps for background migrationsSean McGivern2018-04-181-3/+12
| | | | | 1. We can't just steal from the queue, in case there was a problem with Sidekiq. 2. We need to consider import / export.
* [docs] Info rescheduling background migrationsbvl-fix-concurrent-fork-network-migrationsBob Van Landuyt2018-02-081-0/+12
|
* doc: Spelling fixesVille Skyttä2018-01-191-1/+1
|
* Consistently schedule Sidekiq jobsdm-application-workerDouwe Maan2017-12-051-5/+5
|
* Document manual cleanup after background migration stealingdocument-background-migration-stealingSean McGivern2017-09-251-1/+28
|
* Update the update guides for background migrationsYorick Peterse2017-08-041-0/+9
| | | | | | | | The introduction of background migrations means some of our requirements for online upgrades have to be adjusted / clarified. See https://gitlab.com/gitlab-org/gitlab-ce/issues/35939 for more information.
* Copy-edit background migrations guidelinesGrzegorz Bizon2017-07-211-7/+13
|
* Extend background migration development guidelinesGrzegorz Bizon2017-07-201-0/+30
|
* Improve code examples in background migrations docsGrzegorz Bizon2017-07-071-4/+2
|
* Make it possible to schedule bg migrations in bulkGrzegorz Bizon2017-07-071-4/+15
|
* Add the ability to perform background migrationsYorick Peterse2017-06-121-0/+205
Background migrations can be used to perform long running data migrations without these blocking a deployment procedure. See MR https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/11854 for more information.