Skip to content

Draft: Reschedule background migration to backfill `integrations.type_new`

Markus Koller requested to merge 333507-fix-failed-batched-migration-jobs into master

What does this MR do?

This batched background migration failed due to timeouts caused by the automatic batch size optimization.

This adds another post-deployment migration to split up and retry all of the failed jobs.

Follow-up to !66928 (comment 643866372)

Issue: #333507 (closed), part of the epic &2504 (closed) to rename "services" to "integrations", and specifically the child epic &6177 (closed).

Migration output

$ rails db:migrate:up VERSION=20210805120749
== 20210805120749 RescheduleBackfillIntegrationsTypeNew: migrating ============
== 20210805120749 RescheduleBackfillIntegrationsTypeNew: migrated (0.0480s) ===

$ rails db:migrate:down VERSION=20210805120749
== 20210805120749 RescheduleBackfillIntegrationsTypeNew: reverting ============
== 20210805120749 RescheduleBackfillIntegrationsTypeNew: reverted (0.0000s) ===

Does this MR meet the acceptance criteria?

Conformity

Availability and Testing

Related to #333507 (closed)

Edited by Markus Koller

Merge request reports