Capsule Syncs are Taking Significantly Longer After Upgrading to 6.7.2

Environment

• Satellite 6.7.2

Issue

• Running Satellite 6.6, Capsule syncs took a reasonable amount of time, both when running sequentially or in parallel
• After upgrading to 6.7.2, one Capsule sync standalone or also multiple ones concurrently takes several times more than before

Resolution

• In the Web UI, navigate to Administrator => Settings, and select the Content tab. Find the setting labeled Batch size to sync repositories in. The default setting in 6.7.2 is set to 25. Increase this number to 100 or 200 and see if capsule sync times improve. This number can be increased, however, this will increase the load on Satellite, as it increases the load on dynflowd/foreman-tasks. Purely from Capsyle sync performance, the best values were achieved with value 5000 - with an impact to other tasks esp. REX.

For more KB articles/solutions related to Red Hat Satellite 6.x Capsule Sync Issues, please refer to the Consolidated Troubleshooting Article for Red Hat Satellite 6.x Capsule Sync Issues

Root Cause

• The Batch size to sync repositories in setting was changed to 25 as of Satellite 6.7.2. Prior to 6.7.2, this setting was 10,000. The number has been brought down to ensure stability, by lowering the load in the dynflowd/foreman-tasks service. The downside, this can increase the sync times for Capsules.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.