gitlab-org--gitlab-foss/app/workers/background_migration_worker.rb

# frozen_string_literal: true

class BackgroundMigrationWorker # rubocop:disable Scalability/IdempotentWorker
  include BackgroundMigration::SingleDatabaseWorker

  def self.tracking_database
    @tracking_database ||= Gitlab::BackgroundMigration::DEFAULT_TRACKING_DATABASE
  end
end
Enable frozen string literals for app/workers/*.rb 2018-06-27 03:23:28 -04:00			`# frozen_string_literal: true`

Add latest changes from gitlab-org/gitlab@master 2020-02-19 13:09:10 -05:00			`class BackgroundMigrationWorker # rubocop:disable Scalability/IdempotentWorker`
Add latest changes from gitlab-org/gitlab@master 2021-12-01 13:15:19 -05:00			`include BackgroundMigration::SingleDatabaseWorker`
Add the ability to perform background migrations 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. 2017-06-02 11:12:36 -04:00
Add latest changes from gitlab-org/gitlab@master 2021-12-01 13:15:19 -05:00			`def self.tracking_database`
Add latest changes from gitlab-org/gitlab@master 2021-12-16 22:12:52 -05:00			`@tracking_database \|\|= Gitlab::BackgroundMigration::DEFAULT_TRACKING_DATABASE`
Respond to DB health in background migrations 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. 2018-07-19 11:16:47 -04:00			`end`
Add the ability to perform background migrations 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. 2017-06-02 11:12:36 -04:00			`end`