Module: Gitlab::Database::Migrations::BackgroundMigrationHelpers
- Included in:
- Gitlab::Database::MigrationHelpers
- Defined in:
- lib/gitlab/database/migrations/background_migration_helpers.rb
Constant Summary collapse
- BATCH_SIZE =
Number of rows to process per job
1_000
- JOB_BUFFER_SIZE =
Number of jobs to bulk queue at a time
1_000
Instance Method Summary collapse
- #delete_job_tracking(class_name, status: 'succeeded') ⇒ Object
-
#delete_queued_jobs(class_name) ⇒ Object
rubocop: enable Style/ArgumentsForwarding.
-
#finalize_background_migration(class_name, delete_tracking_jobs: ['succeeded']) ⇒ Object
Force a background migration to complete.
-
#migrate_in(*args, coordinator: coordinator_for_tracking_database) ⇒ Object
rubocop: disable Style/ArgumentsForwarding Reason: the default argument will not apply if we just forward via ‘…`.
-
#queue_background_migration_jobs_by_range_at_intervals(model_class, job_class_name, delay_interval, batch_size: BATCH_SIZE, other_job_arguments: [], initial_delay: 0, track_jobs: false, primary_column_name: :id) ⇒ Object
Queues background migration jobs for an entire table in batches.
-
#requeue_background_migration_jobs_by_range_at_intervals(job_class_name, delay_interval, batch_size: BATCH_SIZE, initial_delay: 0) ⇒ Object
Requeue pending jobs previously queued with #queue_background_migration_jobs_by_range_at_intervals.
Instance Method Details
#delete_job_tracking(class_name, status: 'succeeded') ⇒ Object
220 221 222 223 224 |
# File 'lib/gitlab/database/migrations/background_migration_helpers.rb', line 220 def delete_job_tracking(class_name, status: 'succeeded') status = Array(status).map { |s| Gitlab::Database::BackgroundMigrationJob.statuses[s] } jobs = Gitlab::Database::BackgroundMigrationJob.where(status: status).for_migration_class(class_name) jobs.each_batch { |batch| batch.delete_all } end |
#delete_queued_jobs(class_name) ⇒ Object
rubocop: enable Style/ArgumentsForwarding
212 213 214 215 216 217 218 |
# File 'lib/gitlab/database/migrations/background_migration_helpers.rb', line 212 def delete_queued_jobs(class_name) coordinator_for_tracking_database.steal(class_name) do |job| job.delete false end end |
#finalize_background_migration(class_name, delete_tracking_jobs: ['succeeded']) ⇒ Object
Force a background migration to complete.
WARNING: This method will block the caller and move the background migration from an asynchronous migration to a synchronous migration.
-
Steal work from sidekiq and perform immediately (avoid duplicates generated by step 2).
-
Process any pending tracked jobs.
-
Steal work from sidekiq and perform immediately (clear anything left from step 2).
-
Optionally remove job tracking information.
This method does not garauntee that all jobs completed successfully. It can only be used if the previous background migration used the queue_background_migration_jobs_by_range_at_intervals helper.
166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 |
# File 'lib/gitlab/database/migrations/background_migration_helpers.rb', line 166 def finalize_background_migration(class_name, delete_tracking_jobs: ['succeeded']) if transaction_open? raise 'The `#finalize_background_migration` can not be run inside a transaction, ' \ 'you can disable transactions by calling disable_ddl_transaction! ' \ 'in the body of your migration class' end if background_migration_restrict_gitlab_migration_schemas&.any? raise 'The `#finalize_background_migration` cannot use `restrict_gitlab_migration:`. ' \ 'The `#finalize_background_migration` needs to be executed on all databases since ' \ 'each database has its own queue of background migrations.' end job_coordinator = coordinator_for_tracking_database with_restored_connection_stack do # Since we are running trusted code (background migration class) allow to execute any type of finalize Gitlab::Database::QueryAnalyzers::RestrictAllowedSchemas.with_suppressed do # Empty the sidekiq queue. job_coordinator.steal(class_name) # Process pending tracked jobs. jobs = Gitlab::Database::BackgroundMigrationJob.pending.for_migration_class(class_name) jobs.find_each do |job| job_coordinator.perform(job.class_name, job.arguments) end # Empty the sidekiq queue. job_coordinator.steal(class_name) # Delete job tracking rows. delete_job_tracking(class_name, status: delete_tracking_jobs) if delete_tracking_jobs end end end |
#migrate_in(*args, coordinator: coordinator_for_tracking_database) ⇒ Object
rubocop: disable Style/ArgumentsForwarding Reason: the default argument will not apply if we just forward via ‘…`
205 206 207 208 209 |
# File 'lib/gitlab/database/migrations/background_migration_helpers.rb', line 205 def migrate_in(*args, coordinator: coordinator_for_tracking_database) with_migration_context do coordinator.perform_in(*args) end end |
#queue_background_migration_jobs_by_range_at_intervals(model_class, job_class_name, delay_interval, batch_size: BATCH_SIZE, other_job_arguments: [], initial_delay: 0, track_jobs: false, primary_column_name: :id) ⇒ Object
Queues background migration jobs for an entire table in batches. The default batching column used is the standard primary key ‘id`. Each job is scheduled with a `delay_interval` in between. If you use a small interval, then some jobs may run at the same time.
model_class - The table or relation being iterated over job_class_name - The background migration job class as a string delay_interval - The duration between each job’s scheduled time (must respond to ‘to_f`) batch_size - The maximum number of rows per job other_arguments - Other arguments to send to the job track_jobs - When this flag is set, creates a record in the background_migration_jobs table for each job that is scheduled to be run. These records can be used to trace execution of the background job, but there is no builtin support to manage that automatically at this time. You should only set this flag if you are aware of how it works, and intend to manually cleanup the database records in your background job. primary_column_name - The name of the primary key column if the primary key is not `id`
*Returns the final migration delay*
Example:
class Route < ActiveRecord::Base
include EachBatch
self.table_name = 'routes'
end
queue_background_migration_jobs_by_range_at_intervals(Route, 'ProcessRoutes', 1.minute)
Where the model_class includes EachBatch, and the background migration exists:
class Gitlab::BackgroundMigration::ProcessRoutes
def perform(start_id, end_id)
# do something
end
end
43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 |
# File 'lib/gitlab/database/migrations/background_migration_helpers.rb', line 43 def queue_background_migration_jobs_by_range_at_intervals(model_class, job_class_name, delay_interval, batch_size: BATCH_SIZE, other_job_arguments: [], initial_delay: 0, track_jobs: false, primary_column_name: :id) if transaction_open? raise 'The `#queue_background_migration_jobs_by_range_at_intervals` can not be run inside a transaction, ' \ 'you can disable transactions by calling disable_ddl_transaction! ' \ 'in the body of your migration class' end # Background Migrations do not work well for in cases requiring to update `gitlab_shared` # Once the decomposition is done, enqueued jobs for `gitlab_shared` tables (on CI database) # will not be executed since the queue (which is stored in Redis) is tied to main database, not to schema. # The batched background migrations do not have those limitations since the tracking tables # are properly database-only. if background_migration_restrict_gitlab_migration_schemas&.include?(:gitlab_shared) raise 'The `#queue_background_migration_jobs_by_range_at_intervals` cannot " \ "use `restrict_gitlab_migration:` " with `:gitlab_shared`. ' \ 'Background migrations do encode migration worker which is tied to a given database. ' \ 'After split this worker will not be properly duplicated into decomposed database. ' \ 'Use batched background migrations instead that do support well working across all databases.' end raise "#{model_class} does not have an ID column of #{primary_column_name} to use for batch ranges" unless model_class.column_names.include?(primary_column_name.to_s) raise "#{primary_column_name} is not an integer or string column" unless [:integer, :string].include?(model_class.columns_hash[primary_column_name.to_s].type) job_coordinator = coordinator_for_tracking_database # To not overload the worker too much we enforce a minimum interval both # when scheduling and performing jobs. delay_interval = [delay_interval, job_coordinator.minimum_interval].max final_delay = 0 batch_counter = 0 model_class.each_batch(of: batch_size, column: primary_column_name) do |relation, index| max = relation.arel_table[primary_column_name].maximum min = relation.arel_table[primary_column_name].minimum start_id, end_id = relation.pick(min, max) # `SingleDatabaseWorker.bulk_perform_in` schedules all jobs for # the same time, which is not helpful in most cases where we wish to # spread the work over time. final_delay = initial_delay + delay_interval * index full_job_arguments = [start_id, end_id] + other_job_arguments track_in_database(job_class_name, full_job_arguments) if track_jobs migrate_in(final_delay, job_class_name, full_job_arguments, coordinator: job_coordinator) batch_counter += 1 end duration = initial_delay + delay_interval * batch_counter say <<~SAY Scheduled #{batch_counter} #{job_class_name} jobs with a maximum of #{batch_size} records per batch and an interval of #{delay_interval} seconds. The migration is expected to take at least #{duration} seconds. Expect all jobs to have completed after #{Time.zone.now + duration}." SAY final_delay end |
#requeue_background_migration_jobs_by_range_at_intervals(job_class_name, delay_interval, batch_size: BATCH_SIZE, initial_delay: 0) ⇒ Object
Requeue pending jobs previously queued with #queue_background_migration_jobs_by_range_at_intervals
This method is useful to schedule jobs that had previously failed. It can only be used if the previous background migration used job tracking like the queue_background_migration_jobs_by_range_at_intervals helper.
job_class_name - The background migration job class as a string delay_interval - The duration between each job’s scheduled time batch_size - The maximum number of jobs to fetch to memory from the database.
111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 |
# File 'lib/gitlab/database/migrations/background_migration_helpers.rb', line 111 def requeue_background_migration_jobs_by_range_at_intervals(job_class_name, delay_interval, batch_size: BATCH_SIZE, initial_delay: 0) if transaction_open? raise 'The `#requeue_background_migration_jobs_by_range_at_intervals` can not be run inside a transaction, ' \ 'you can disable transactions by calling disable_ddl_transaction! ' \ 'in the body of your migration class' end if background_migration_restrict_gitlab_migration_schemas&.any? raise 'The `#requeue_background_migration_jobs_by_range_at_intervals` cannot use `restrict_gitlab_migration:`. ' \ 'The `#requeue_background_migration_jobs_by_range_at_intervals` needs to be executed on all databases since ' \ 'each database has its own queue of background migrations.' end job_coordinator = coordinator_for_tracking_database # To not overload the worker too much we enforce a minimum interval both # when scheduling and performing jobs. delay_interval = [delay_interval, job_coordinator.minimum_interval].max final_delay = 0 job_counter = 0 jobs = Gitlab::Database::BackgroundMigrationJob.pending.where(class_name: job_class_name) jobs.each_batch(of: batch_size) do |job_batch| job_batch.each do |job| final_delay = initial_delay + delay_interval * job_counter migrate_in(final_delay, job_class_name, job.arguments, coordinator: job_coordinator) job_counter += 1 end end duration = initial_delay + delay_interval * job_counter say <<~SAY Scheduled #{job_counter} #{job_class_name} jobs with an interval of #{delay_interval} seconds. The migration is expected to take at least #{duration} seconds. Expect all jobs to have completed after #{Time.zone.now + duration}." SAY duration end |