Project

Profile

Help

Story #8470

closed

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

Added by ttereshc almost 3 years ago. Updated almost 3 years 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.

Also available in: Atom PDF