From f2e45997243d62bde376b99cdbf4b8496e79e8a2 Mon Sep 17 00:00:00 2001 From: Eric Ju Date: Sat, 22 Nov 2025 00:13:19 -0500 Subject: [PATCH] migration: Bump leftover migration ID to rerun The leftover migration previously used ID 1, and it has already run across the gitlab-org group. During some CNY incidents, Gitaly transactions were paused and the leftover migration was disabled. Now that Gitaly transactions on CNY have been re-enabled and we want to turn leftover migration back on, the existing migration will not run again because it has already been marked as completed. To ensure that the migration runs a second time, we need to bump the migration ID so that Gitaly recognizes it as a new migration task. This commit increments the leftover migration ID to trigger it to run again. --- .../storagemgr/partition/migration/id/migration_task_ids.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/internal/gitaly/storage/storagemgr/partition/migration/id/migration_task_ids.go b/internal/gitaly/storage/storagemgr/partition/migration/id/migration_task_ids.go index 747027bbd1..d39c9ebbc0 100644 --- a/internal/gitaly/storage/storagemgr/partition/migration/id/migration_task_ids.go +++ b/internal/gitaly/storage/storagemgr/partition/migration/id/migration_task_ids.go @@ -6,7 +6,7 @@ import "math" // the last migration it performed. Subsequent migration jobs should always use increasing numbers. const ( // LeftoverFile is the migration ID of a leftover file migration. - LeftoverFile = 1 + LeftoverFile = 2 // Reftable is a placeholder value. The Reftable migration uses a special ID marked as math.MaxUint64 because // retable migration isn't wired into the migration manager like other migrations. -- GitLab