Skip to content

Use sub-batches in BackfillIntegrationsTypeNew background migration

Markus Koller requested to merge 333507-use-sub-batches into master

What does this MR do?

Previously we were ignoring the sub_batch_size argument and using start_id and stop_id directly, which led to timeouts on staging.

The migration succeeded on production, but this change should help increase the chances for the migration to succeed on self-managed instances as well.

Follow-up to !66928 (merged), in response to !67602 (comment 647562361)

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

Background Migration Details

See data in previous MR: !66928 (diffs)

The difference is that we're now also sub-dividing each batch into smaller batches, so the queries should be more efficient.

Unfortunately I can't get realistic query plans out of #database-lab because the migration has already succeeded there, i.e. most records now already have type_new set 😉

database reviewers: Let me know if you need more info here.

Does this MR meet the acceptance criteria?

Conformity

Availability and Testing

Related to #333507 (closed)

Edited by Markus Koller

Merge request reports

Loading