Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be available on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 1740222 - ISS slave takes much longer to sync content after upgrade to 5.8
Summary: ISS slave takes much longer to sync content after upgrade to 5.8
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Satellite Synchronization
Version: 580
Hardware: All
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Michael Mráka
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-12 13:49 UTC by Julio Entrena Perez
Modified: 2019-08-15 10:47 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-15 10:47:14 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Julio Entrena Perez 2019-08-12 13:49:37 UTC 
Description of problem:
The time required for a Satellite 5.8 ISS slave to synchronise content has grown by an order of magnitude vs Satellite 5.7.

Version-Release number of selected component (if applicable):
spacewalk-backend-tools-2.5.3-177.el6sat.noarch

How reproducible:
Always

Steps to Reproduce:
1. On a Satellite 5.7 which is a ISS slave, run satellite-sync and measure time taken to complete the sync
2. Upgrade said ISS slave Satellite 5.7 to Satellite 5.8
3. Re-run same satellite-sync command in step 1 and measure time taken to complete the sync
3.

Actual results:
Best case scneario is sync time doubling, worst case scenario is sync time taking many more times on a 5.8 ISS slave than on a 5.7.

Expected results:
Sync times remain comparable.

Additional info:
Steps "diffing" and "Linking packages to channels" seem to account for most of the increase in sync time.
Comment 4 Julio Entrena Perez 2019-08-15 10:47:14 UTC 
Despite VACUUM was already executed after the upgrade to Satellite 5.8, running VACUUM again, this time with ANALYZE, brought the synchronization times back to what they were before the upgrade to Satellite 5.8.
Note You need to log in before you can comment on or make changes to this bug.