Bug 2000769

Summary:	pulp3: CV publishes with dependency solving and same source repos for copy are not concurrent
Product:	Red Hat Satellite	Reporter:	Tanya Tereshchenko <ttereshc>
Component:	Pulp	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED ERRATA	QA Contact:	Jitendra Yejare <jyejare>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.10.0	CC:	ahumbe, ggainey, jyejare, ltran, pcreech, rchan, ttereshc, zhunting
Target Milestone:	6.11.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-07-05 14:29:38 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1994397, 2035873
Bug Blocks:

Description Tanya Tereshchenko 2021-09-02 20:56:51 UTC

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

Comment 2 pulp-infra@redhat.com 2021-09-02 21:07:15 UTC

The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.

Comment 3 pulp-infra@redhat.com 2021-09-02 21:07:16 UTC

The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.

Comment 4 pulp-infra@redhat.com 2021-09-02 21:07:25 UTC

The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.

Comment 5 pulp-infra@redhat.com 2021-09-02 21:07:26 UTC

The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.

Comment 6 pulp-infra@redhat.com 2021-09-02 22:07:59 UTC

All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.

Comment 9 Brad Buckingham 2021-09-28 16:48:23 UTC

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?

Comment 16 Jitendra Yejare 2021-12-06 11:17:20 UTC

Comment 21 Jitendra Yejare 2022-04-07 19:09:05 UTC

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.

Comment 24 errata-xmlrpc 2022-07-05 14:29:38 UTC

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