Hide Forgot
Description of problem: Some customers are facing issue related to performance and DB locking when the load is high "a bunch of Content Hosts + virt-who process + some API scripts + huge virtualization environment with a ton of Hypervisors and Guests" Version-Release number of selected component (if applicable): 6.3.4 How reproducible: 100% Steps to Reproduce: 1. Create an environment according to above 2. Keep the monitoring on the PG 3. ps -ef | grep wait Actual results: Some process like "UPDATE: waiting" and waiting on the PG activities table, as consequence, this value just increase and at the end of the day PG just stop and Satellite fail. Expected results: Satellite be able to handle all requests and move forward. Additional info:
Waldirio, We are adding tuning profiles in installer as part of 6.7 which will setup postgres tunings which are listed in satellite-support project. Do you think it is good enough? or is there anything else you like to see as part of this bug?
Hello sthirung, Looks good to me. I'm not sure if the tuning above (autovacuum treshoold for some tables) will be added, I believe to be super valid. Thank you. Waldirio
Verified with 6.7 Snap10. foreman-installer version: # rpm -q foreman-installer foreman-installer-1.24.1.5-1.el7sat.noarch Verified points: * Deployment size successfully applied using satellite-installer. # satellite-installer --tuning medium --disable-system-checks Installing Done [100%] [................................................................................................................................] Success! # grep tuning /etc/foreman-installer/scenarios.d/satellite.yaml tuning: medium :tuning: medium Set postgresql parameters are below: postgresql::server::config_entries: max_connections: 1000 shared_buffers: 4GB checkpoint_segments: 32 effective_cache_size: 16GB autovacuum_vacuum_cost_limit: 2000
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/RHSA-2020:1454