Description of problem: If i create 8 ContentViews that contains the same (i guess even 1 same repo is already enough) source repos and enable the dependency solving then the tasks are not parallelized in pulp3. Looking at the resources and locking code for the tasks it looks like the locking is always done in a write-exclusive way. Steps to Reproduce: 1. Create 8 pulp workers 2. Sync a few big RHEL7 repos 3. Create 8 CVs with the use ~5 big RHEL7 repos 4. Publish all 8 CVs concurrent with dep solving enabled Actual results: Not all 8 pulp workers are handling the work. it looks like especially the Copy of the content kept in waiting until the previous work is finished Expected results: All 8 CVs are published at the same time, almost all 8 pulp workers are busy also during copy of content from the same source repo Additional info: With Pulp2 the tasks was processed nicely in parallel
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.
For this one, will the CV publish finish successfully? What would be the publish time for the scenario described in the description with and without the fix? Are we talking minutes, hours, days?
@
Verified! @Satellite 6.11 snap 15 RPMs: python38-pulpcore-3.16.3-1.el8pc.noarch python38-pulp-rpm-3.17.3-2.el8pc.noarch Steps to Reproduce: 1. Created 6 pulp workers as my satellite system has 6 cores. 2. Synced 5 big RHEL7 repos 3. Created 6 CVs with the use of 5 big RHEL7 repos 4. Published all 6 CVs concurrent with dep solving enabled. Actual results: All 6 CVs are published at the same time, almost all 6 pulp workers were busy also during copy of content from the same source repo.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: Satellite 6.11 Release), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:5498