Project

Profile

Help

Story #8470

As a user, I can configure the batch size for the content premigration

Added by ttereshc about 1 month ago. Updated 29 days ago.

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

100%

Estimated time:
Platform Release:
Groomed:
Yes
Sprint Candidate:
No
Tags:
Katello
Sprint:
Sprint 94
Quarter:
Q2-2021

Description

When migration is run on the slow machine, the mongo cursor can timeout if some errata pkglist are especially large or there are many pkglists to process (old [long-running] pulp 2 system) .

In order not to slow down the process for everyone, introduce a configuration option CONTENT_PREMIGRATION_BATCH_SIZE.
It will default to 1000 and the recommendation for a slow system would be 50-100.

Associated revisions

Revision 007f8071 View on GitHub
Added by ttereshc about 1 month ago

Add CONTENT_PREMIGRATION_BATCH_SIZE configuration option

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

Revision 007f8071 View on GitHub
Added by ttereshc about 1 month ago

Add CONTENT_PREMIGRATION_BATCH_SIZE configuration option

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

Revision 007f8071 View on GitHub
Added by ttereshc about 1 month ago

Add CONTENT_PREMIGRATION_BATCH_SIZE configuration option

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

History

#1 Updated by ttereshc about 1 month ago

  • Description updated (diff)

#2 Updated by ipanova@redhat.com about 1 month ago

  • Groomed changed from No to Yes

#3 Updated by ttereshc about 1 month ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to ttereshc
  • Sprint set to Sprint 94

#4 Updated by ttereshc about 1 month ago

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

#5 Updated by ttereshc 29 days ago

  • Sprint/Milestone set to 0.11.0

#6 Updated by pulpbot 29 days ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Please register to edit this issue

Also available in: Atom PDF