Bug 1419128

Summary:	Capsule sync in 6.2 is slower than in 6.1
Product:	Red Hat Satellite	Reporter:	Dennis Kliban <dkliban>
Component:	Pulp	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED WONTFIX	QA Contact:	Katello QA List <katello-qa-list>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.2.7	CC:	bbuckingham, bill.scherer, bmbouter, cduryee, daviddavis, ddolguik, dkliban, ggainey, gkeegan, ipanova, jcallaha, jentrena, mhrivnak, michael.hanson, pcreech, rballang, rchan, tcarlin, ttereshc
Target Milestone:	Unspecified	Keywords:	PrioBumpPM, 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:	2018-09-04 18:05:16 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Dennis Kliban 2017-02-03 16:18:50 UTC

Description of problem:

When syncing a capsule with many repositories that all have the same content, each repository still takes a few minutes to sync. 


How reproducible:

All the time

Steps to Reproduce:
1. Create a LCE in satellite with the RHEL7 repository.
2. Create multiple more LCEs in satellite with RHEL7 repository.
3. Create a capsule that is associated with all the LCEs
4. Sync the capsule



Additional info:

This change in behavior in Satellite 6.2 can be attributed to the change in how Pulp is used on a capsule. Satellite 6.1 used Pulp nodes to perform syncs and publishes on the capsule. Pulp nodes did not require parsing of repository metadata before transmitting any data. Satellite 6.2 uses a natural Pulp sync. This sync requires parsing repository metadata. So even if there is no content to sync, it still takes some time to parse the metadata. 

This issue is related to https://bugzilla.redhat.com/show_bug.cgi?id=1395777

Comment 3 pulp-infra@redhat.com 2017-02-03 23:31:37 UTC

The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.

Comment 4 pulp-infra@redhat.com 2017-02-03 23:31:40 UTC

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

Comment 5 Michael Hrivnak 2017-02-05 08:37:20 UTC

The scope of this problem is limited to mostly the first sync of a new capsule, or the first sync after lots of repos have been added to a capsule, right?

In normal operation for yum repos at least, when most repos do not have any changes, the syncs will finish in just a few seconds because of the repomd.xml serial number optimization.

It should also be noted that while this may cost some extra time on the sync end, we are saving a huge amount of time and storage space on the Satellite itself by no longer publishing node metadata. For most customers, I suspect the net trade-off is a substantial improvement in overall performance.

Comment 6 Michael Hrivnak 2017-02-05 08:38:07 UTC

I'm moving to the Pulp component since the next steps are for the Pulp team.

Comment 7 Michael Hrivnak 2017-02-05 08:50:09 UTC

Dennis, what do you think about making this an RFE to make pulp-pulp sync more efficient? That would match the upstream issue.

Comment 13 Bryan Kearney 2018-09-04 18:05:16 UTC

Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.

Comment 14 pulp-infra@redhat.com 2020-12-03 17:11:09 UTC

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