| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Add latest changes from gitlab-org/gitlab@14-8-stable-eev14.8.0-rc42 | GitLab Bot | 2022-02-18 | 1 | -4/+0 |
| | | |||||
| * | Add latest changes from gitlab-org/gitlab@14-6-stable-eev14.6.0-rc42 | GitLab Bot | 2021-12-20 | 1 | -112/+5 |
| | | |||||
| * | Add latest changes from gitlab-org/gitlab@14-3-stable-eev14.3.0-rc42 | GitLab Bot | 2021-09-20 | 1 | -8/+15 |
| | | |||||
| * | Add latest changes from gitlab-org/gitlab@14-2-stable-eev14.2.0-rc42 | GitLab Bot | 2021-08-19 | 1 | -0/+2 |
| | | |||||
| * | Add latest changes from gitlab-org/gitlab@13-12-stable-eev13.12.0-rc42 | GitLab Bot | 2021-05-19 | 1 | -0/+2 |
| | | |||||
| * | Add latest changes from gitlab-org/gitlab@13-6-stable-eev13.6.0-rc42 | GitLab Bot | 2020-11-19 | 1 | -22/+35 |
| | | |||||
| * | Add latest changes from gitlab-org/gitlab@13-5-stable-eev13.5.0-rc42 | GitLab Bot | 2020-10-21 | 1 | -1/+3 |
| | | |||||
| * | Add latest changes from gitlab-org/gitlab@13-1-stable-ee | GitLab Bot | 2020-06-18 | 1 | -0/+1 |
| | | |||||
| * | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2020-04-15 | 1 | -0/+1 |
| | | |||||
| * | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2020-03-24 | 1 | -1/+1 |
| | | |||||
| * | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2020-02-19 | 1 | -11/+13 |
| | | |||||
| * | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-10-18 | 1 | -0/+2 |
| | | |||||
| * | Further remove code branches by database type | Andreas Brandl | 2019-07-29 | 1 | -2/+0 |
| | | | | | | | | | We dropped MySQL support and a lot of mysql specific code has been removed in https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/29608. This comes in from the other direction and removes any `if postgresql?` branches. | ||||
| * | Remove feature flag from BackgroundMigrationWorker | Yorick Peterse | 2018-08-28 | 1 | -13/+1 |
| | | | | | | | The feature has been running on GitLab.com for a while now, without any problems. This commit removes the eature flag, and enables the feature for all users. | ||||
| * | Respond to DB health in background migrations | Yorick Peterse | 2018-08-06 | 1 | -7/+54 |
| | | | | | | | | | | | | | | | | | | | | 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. | ||||
| * | Enable frozen string literals for app/workers/*.rb | gfyoung | 2018-06-27 | 1 | -0/+2 |
| | | |||||
| * | Run background migrations with a minimum intervaldelay-background-migrations | Yorick Peterse | 2018-01-05 | 1 | -1/+44 |
| | | | | | | | | | | | | | | | | This adds a minimum interval to BackgroundMigrationWorker, ensuring background migrations of the same class only run once every 5 minutes. This prevents a thundering herd problem where scheduled migrations all run at once due to their delays having been expired (e.g. as the result of a queue being paused for a long time). If a job was recently executed it's rescheduled with a delay that equals the remaining time of the job's lease. This means that if the lease expires in two minutes we only need to wait two minutes, instead of five. Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/41624 | ||||
| * | Consistently schedule Sidekiq jobsdm-application-worker | Douwe Maan | 2017-12-05 | 1 | -28/+0 |
| | | |||||
| * | Add ApplicationWorker and make every worker include it | Douwe Maan | 2017-12-05 | 1 | -2/+1 |
| | | |||||
| * | Improve exception description in bg migrations | Grzegorz Bizon | 2017-07-07 | 1 | -1/+3 |
| | | |||||
| * | Add description to exception in bg migrations worker | Grzegorz Bizon | 2017-07-07 | 1 | -1/+1 |
| | | |||||
| * | Use integers to schedule delayed background migrations | Grzegorz Bizon | 2017-07-07 | 1 | -2/+2 |
| | | |||||
| * | Use ActiveRecord 5 batching to schedule bg migration | Grzegorz Bizon | 2017-07-07 | 1 | -1/+1 |
| | | |||||
| * | Make it possible to schedule bg migrations in bulk | Grzegorz Bizon | 2017-07-07 | 1 | -2/+16 |
| | | |||||
| * | Add the ability to perform background migrations | Yorick Peterse | 2017-06-12 | 1 | -0/+23 |
| 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. | |||||
 |
index : delta/gitlab/gitlab-ce.git | |
| gitlab.com: gitlab-org/gitlab-ce.git |
| summaryrefslogtreecommitdiff |