Project

Profile

Help

Issue #9564

CursorNotFound errors when migrating a large number of deb_components

Added by quba42 27 days ago. Updated 2 days ago.

Status:
MODIFIED
Priority:
Normal
Assignee:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Platform Release:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

Since each deb_component creates a large number of Pulp2to3Content, this content type should use a significantly lower batch size than other content types during pre_migration in order to avoid CursorNotFound errors.

Since deb_components can vary considerably in size (number of packages they contain), it would be good to make the batch size configurable for this type, using something like a DEB_COMPONENT_BATCH_SIZE setting.

Associated revisions

Revision f5d9b8ae View on GitHub
Added by quba42 2 days ago

Add DEB_COMPONENT_BATCH_SIZE setting

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

Since each deb_components creates a large number of Pulp2to3Content we need a much lower batch size for this type.

Revision f5d9b8ae View on GitHub
Added by quba42 2 days ago

Add DEB_COMPONENT_BATCH_SIZE setting

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

Since each deb_components creates a large number of Pulp2to3Content we need a much lower batch size for this type.

Revision f5d9b8ae View on GitHub
Added by quba42 2 days ago

Add DEB_COMPONENT_BATCH_SIZE setting

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

Since each deb_components creates a large number of Pulp2to3Content we need a much lower batch size for this type.

History

#1 Updated by quba42 2 days ago

  • Status changed from NEW to MODIFIED

Please register to edit this issue

Also available in: Atom PDF