Project

Profile

Help

Story #7779

closed

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 2 years ago. Updated almost 2 years 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.
Actions #1

Updated by ttereshc about 2 years ago

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

Actions #2

Updated by ttereshc about 2 years ago

  • Tags Katello added
Actions #3

Updated by ttereshc almost 2 years ago

  • Sprint/Milestone set to 0.9.0
Actions #4

Updated by ttereshc almost 2 years ago

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

Updated by ttereshc almost 2 years ago

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

Actions #6

Updated by ttereshc almost 2 years ago

  • Status changed from ASSIGNED to POST

Added by ttereshc almost 2 years ago

Revision 7c200b5f

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

Added by ttereshc almost 2 years ago

Revision 7c200b5f

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

Added by ttereshc almost 2 years ago

Revision 7c200b5f

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

Actions #8

Updated by ttereshc almost 2 years ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100
Actions #9

Updated by ttereshc almost 2 years ago

  • Sprint/Milestone changed from 0.9.0 to 0.8.0
Actions #10

Updated by pulpbot almost 2 years ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Also available in: Atom PDF