Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Add latest changes from gitlab-org/gitlab@14-7-stable-eev14.7.0-rc42 | GitLab Bot | 2022-01-20 | 1 | -64/+35 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@14-6-stable-eev14.6.0-rc42 | GitLab Bot | 2021-12-20 | 1 | -5/+8 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@14-3-stable-eev14.3.0-rc42 | GitLab Bot | 2021-09-20 | 1 | -6/+15 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@14-2-stable-eev14.2.0-rc42 | GitLab Bot | 2021-08-19 | 1 | -13/+18 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@14-1-stable-eev14.1.0-rc42 | GitLab Bot | 2021-07-20 | 1 | -4/+81 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@14-0-stable-eev14.0.0-rc42 | GitLab Bot | 2021-06-16 | 1 | -33/+82 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@13-11-stable-eev13.11.0-rc43 | GitLab Bot | 2021-04-20 | 1 | -0/+8 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@13-7-stable-eev13.7.0-rc42 | GitLab Bot | 2020-12-17 | 1 | -2/+2 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@13-6-stable-eev13.6.0-rc42 | GitLab Bot | 2020-11-19 | 1 | -1/+23 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@13-5-stable-eev13.5.0-rc42 | GitLab Bot | 2020-10-21 | 1 | -1/+22 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@13-3-stable-ee | GitLab Bot | 2020-08-20 | 1 | -5/+5 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@13-1-stable-ee | GitLab Bot | 2020-06-18 | 1 | -2/+2 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@13-0-stable-ee | GitLab Bot | 2020-05-20 | 1 | -8/+3 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2020-03-17 | 1 | -2/+3 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2020-02-19 | 1 | -5/+6 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2020-02-18 | 1 | -1/+1 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2020-01-29 | 1 | -2/+1 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2020-01-22 | 1 | -0/+7 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-12-17 | 1 | -5/+5 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-12-13 | 1 | -1/+6 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-09-24 | 1 | -1/+3 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-09-18 | 1 | -3/+3 |
| | |||||
* | Standardised punctuation at end of sentences | Russell Dickenson | 2019-09-09 | 1 | -4/+4 |
| | |||||
* | Removes regular migrations from background ones | Mayra Cabrera | 2019-09-04 | 1 | -6/+9 |
| | | | | | Specifies that background migrations should be scheduled as post deployment migrations | ||||
* | Update capitalization in /dev docs | Marcel Amirault | 2019-08-27 | 1 | -1/+1 |
| | | | | | Clean up capitalization in /development /gitlab-basics and /install | ||||
* | Make unordered lists conform to styleguidedocs/fix-unordered-list-style | Evan Read | 2019-01-08 | 1 | -3/+3 |
| | | | | - Also makes other minor Markdown fixes that were near the main fixes. | ||||
* | Fix ActiveRecord::Migration deprecations | Yorick Peterse | 2018-12-12 | 1 | -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 Walker | 2018-09-06 | 1 | -20/+20 |
| | |||||
* | Respond to DB health in background migrations | Yorick Peterse | 2018-08-06 | 1 | -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-doc | Oswaldo Ferreira | 2018-07-24 | 1 | -0/+8 |
| | |||||
* | Fixed typos | Pascal Borreli | 2018-04-27 | 1 | -2/+2 |
| | |||||
* | Add more detail to cleanup steps for background migrations | Sean McGivern | 2018-04-18 | 1 | -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-migrations | Bob Van Landuyt | 2018-02-08 | 1 | -0/+12 |
| | |||||
* | doc: Spelling fixes | Ville Skyttä | 2018-01-19 | 1 | -1/+1 |
| | |||||
* | Consistently schedule Sidekiq jobsdm-application-worker | Douwe Maan | 2017-12-05 | 1 | -5/+5 |
| | |||||
* | Document manual cleanup after background migration stealingdocument-background-migration-stealing | Sean McGivern | 2017-09-25 | 1 | -1/+28 |
| | |||||
* | Update the update guides for background migrations | Yorick Peterse | 2017-08-04 | 1 | -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 guidelines | Grzegorz Bizon | 2017-07-21 | 1 | -7/+13 |
| | |||||
* | Extend background migration development guidelines | Grzegorz Bizon | 2017-07-20 | 1 | -0/+30 |
| | |||||
* | Improve code examples in background migrations docs | Grzegorz Bizon | 2017-07-07 | 1 | -4/+2 |
| | |||||
* | Make it possible to schedule bg migrations in bulk | Grzegorz Bizon | 2017-07-07 | 1 | -4/+15 |
| | |||||
* | Add the ability to perform background migrations | Yorick Peterse | 2017-06-12 | 1 | -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. |