Bug 1857359
Summary: | large capsule syncs cause slow processing of dynflow tasks/steps | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Mike McCune <mmccune> |
Component: | Capsule - Content | Assignee: | Justin Sherrill <jsherril> |
Status: | CLOSED ERRATA | QA Contact: | Lukáš Hellebrandt <lhellebr> |
Severity: | unspecified | Docs Contact: | |
Priority: | high | ||
Version: | 6.7.0 | CC: | aeladawy, ahumbe, dgross, dsynk, ehelms, fperalta, iballou, joboyer, jsherril, ktordeur, lhellebr, pcreech, rbertolj, saydas, smajumda, wclark |
Target Milestone: | 6.7.2 | Keywords: | PrioBumpGSS, Triaged |
Target Release: | Unused | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | tfm-rubygem-katello-3.14.0.25-1 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | 1853076 | Environment: | |
Last Closed: | 2020-07-30 20:21:15 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: |
Comment 2
Bryan Kearney
2020-07-15 20:05:25 UTC
Verified with Sat 6.7.2 snap 2.0. This is hard to verify as there is no real reproducer nor is it concretely specified how this bug actually manifests. I had a Satellite, an external Capsule and a Host registered through that Capsule. I tried to cause huge sync load on both Satellite and Capsule. During this time, I tried to also run different tasks on the hosts, e.g. ran a command through remote execution. I measured systems load which was high due to ~25 repos being synced at a time but nothing was unusually or unexpectably slow. Most CPU time was taken by pulp workers which is expected when syncing. I haven't noticed any files growing too much (cache grew a few GBs and shrinked after the operation) or lowered responsibility at any time. The remote commands have been ran correctly and almost immediately. Dynflow log looks ok. To conclude, I haven't noticed any issues while doing a large Capsule sync. 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, 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/RHBA-2020:3255 |