Project

Profile

Help

Issue #7483

RPM Copy API encounters timeouts when copying large quanitites of units

Added by iballou 20 days ago. Updated 5 days ago.

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

Description

With Katello, we are hitting issues with time-outs and request size limits when trying to copy 10s of thousands of content units via the RPM Copy API. To avoid workarounds like implementing our own "batching", it would be best if the RPM Copy API could accept multiple copy requests and do its own batching.

Associated revisions

Revision 61bc0817 View on GitHub
Added by dalley 7 days ago

Fix requests timing out with large copy operations

[nocoverage]

Required PR: https://github.com/pulp/pulpcore/pull/927

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

History

#1 Updated by dalley 20 days ago

  • Sprint set to Sprint 81

The likely problem is the following lines: https://github.com/pulp/pulp_rpm/blob/master/pulp_rpm/app/viewsets.py#L317-L318

Wherein each content href is used to individually look up the corresponding content. 10,000 content = at least individual 10,000 queries being made within the span of the single request.

#2 Updated by dalley 18 days ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to dalley

#3 Updated by rchan 11 days ago

  • Sprint changed from Sprint 81 to Sprint 82

#4 Updated by pulpbot 7 days ago

  • Status changed from ASSIGNED to POST

#6 Updated by dalley 7 days ago

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

#7 Updated by ttereshc 6 days ago

  • Sprint/Milestone set to 3.7.0

#8 Updated by dalley 6 days ago

  • Tracker changed from Story to Issue
  • Subject changed from RPM Copy API should have some sort of batching for large requests to RPM Copy API encounters timeouts when copying large quanitites of units
  • % Done changed from 100 to 0
  • Severity set to 2. Medium
  • Triaged set to No

#9 Updated by pulpbot 5 days ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Please register to edit this issue

Also available in: Atom PDF