Skip to content

Hashed Storage: Prevent a migration and rollback running at the same time

What does this MR do?

Prevents a migration or rollback to be scheduled if the opposite operation is already scheduled.

See example below:

$ rake gitlab:storage:migrate_to_hashed                                                                                                                                         
Enqueuing migration of 10 projects in batches of 200. Done!

$ rake gitlab:storage:rollback_to_legacy
There is already a migration operation in progress, running a rollback at the same time may have unexpected consequences.

What are the relevant issue numbers?

Closes #58739 (closed)

Does this MR meet the acceptance criteria?

Edited by Gabriel Mazetto

Merge request reports