-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
None
Description of problem:
An upstream user reported an issue about slow capsule syncs (2 hours vs 10 minutes) on our upstream forums: https://community.theforeman.org/t/slow-content-proxy-sync/35162
ATIX also reported seeing the issue on "two internal systems": https://community.theforeman.org/t/slow-content-proxy-sync/35162/27
The bug has yet to be reproduced in-house, however, it was discovered that reverting the following Pulpcore patch fixes the issue: https://github.com/pulp/pulpcore/pull/4275
The issue has been identified with some certainty to be caused by differences in PostgreSQL 12 and 13. Pulp develops on 13+, where Satellite uses 12. On PostgreSQL 13, the patch speeds up repository syncing. However, on PostgreSQL 12, the patch can slow syncing down. Based on this comment (https://community.theforeman.org/t/slow-content-proxy-sync/35162/31), there is a change in PostgreSQL 13 that lines up well with the slowdown issue.
The current recommendation is to revert the patch on Pulpcore 3.22 and 3.21, and create a Katello-only patch for Pulpcore 3.28.
Version-Release number of selected component (if applicable):
6.13.5 and up
How reproducible:
Not reproduced by anyone outside of the upstream thread yet
Steps to Reproduce:
No info on reproducing the issue yet.
Actual results:
Hours-longer capsule sync
Expected results:
Regular capsule sync
Additional info:
There are still unknowns to the issue. The only thing that was verified by two users was that reverting the Pulpcore patch above fixes the slowness issue.