Actions
Story #8470
closed
As a user, I can configure the batch size for the content premigration
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.
Updated by ttereshc about 3 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to ttereshc
- Sprint set to Sprint 94
Added by ttereshc about 3 years ago
Added by ttereshc about 3 years ago
Revision 007f8071 | View on GitHub
Add CONTENT_PREMIGRATION_BATCH_SIZE configuration option
Added by ttereshc about 3 years ago
Revision 007f8071 | View on GitHub
Add CONTENT_PREMIGRATION_BATCH_SIZE configuration option
Updated by ttereshc about 3 years ago
- Status changed from ASSIGNED to MODIFIED
- % Done changed from 0 to 100
Applied in changeset pulp:pulp-2to3-migration|007f807105093af563667c59ea5d3dff3ba31337.
Updated by pulpbot about 3 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
.
Add CONTENT_PREMIGRATION_BATCH_SIZE configuration option
closes #8470 https://pulp.plan.io/issues/8470