Project

Profile

Help

Issue #2225

closed

errors when sync plans fire off many concurrent syncs

Added by cduryee over 7 years ago. Updated about 5 years ago.

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

Description

If a user creates 1000 repos and adds a sync plan to sync them all at the same time, many of the syncs will error out.

Ideally, all of the syncs would get tasks created for them and get picked up in order.

NOTE: if concurrent syncs are fired, everything works as expected. The errors seem specific to using sync plans. This appears to happen with both Pulp 2.4 and 2.8.

Actions #1

Updated by bmbouter over 7 years ago

What is the error that occurs?

Would it be possible to post a reproducer? An example of the scheduled sync API request would be fine. Pulp admin would be ideal.

Actions #2

Updated by cduryee over 7 years ago

  • Status changed from NEW to CLOSED - NOTABUG

I put this in but there were further updates to the BZ to indicate this is not the issue.

Closing issue.

Actions #3

Updated by bmbouter about 5 years ago

  • Tags Pulp 2 added

Also available in: Atom PDF