Project

Profile

Help

Story #7779

As a user, a migration re-run is very fast, if there were no or very little changes in pulp 2

Added by ttereshc about 1 year ago. Updated 10 months ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Sprint/Milestone:
Start date:
Due date:
% Done:

100%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Katello
Sprint:
Sprint 90
Quarter:
Q1-2021

Description

Motivation

Users run the migration task multiple times upfront, so the switchover to Pulp 3 happens quickly, within few minutes. Switchover = stop pulp 2 services, run migration for the last time, start using pulp3.

Existing concerns and thoughts

  • Following the same code path as normal migration when no changes have been made in pulp 2 takes a noticeable amount of time. We might need to introduce some shortcuts for the case when nothing has been changed in pulp 2.
  • Same goes to the case when only very few changes have been made.
  • If everything possible is done and no shortcuts are available we might need to look at the performance of the longest steps or rethink the approach.

Associated revisions

Revision 7c200b5f View on GitHub
Added by ttereshc 10 months ago

Only go through the changed repositories on the re-run.

Also improved how repo type is determined for complex plans. There is no need to look at repo-content relations in such case becasue the plugin type is clear from the plan.

closes #7779 https://pulp.plan.io/issues/7779

Revision 7c200b5f View on GitHub
Added by ttereshc 10 months ago

Only go through the changed repositories on the re-run.

Also improved how repo type is determined for complex plans. There is no need to look at repo-content relations in such case becasue the plugin type is clear from the plan.

closes #7779 https://pulp.plan.io/issues/7779

Revision 7c200b5f View on GitHub
Added by ttereshc 10 months ago

Only go through the changed repositories on the re-run.

Also improved how repo type is determined for complex plans. There is no need to look at repo-content relations in such case becasue the plugin type is clear from the plan.

closes #7779 https://pulp.plan.io/issues/7779

History

#1 Updated by ttereshc about 1 year ago

Currently a re-run for a large-ish system (1K repos, 300K rpms) when nothing changed in pulp 2 is taking 13 mins.

#2 Updated by ttereshc about 1 year ago

  • Tags Katello added

#3 Updated by ttereshc 10 months ago

  • Sprint/Milestone set to 0.9.0

#4 Updated by ttereshc 10 months ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to ttereshc
  • Sprint set to Sprint 90
  • Quarter set to Q1-2021

#5 Updated by ttereshc 10 months ago

For a setup with 39K repos and 48M repo-content relations, re-run takes hours.

#6 Updated by ttereshc 10 months ago

  • Status changed from ASSIGNED to POST

#8 Updated by ttereshc 10 months ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100

#9 Updated by ttereshc 10 months ago

  • Sprint/Milestone changed from 0.9.0 to 0.8.0

#10 Updated by pulpbot 10 months ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Please register to edit this issue

Also available in: Atom PDF