Hide Forgot
Description of problem: Applying the tuning for large deployments as per Appendix A of the installation manual, "Increasing Concurrent Content Host Registrations" steps 3 and 4 state: (3) Edit the Foreman Passenger application configuration file /etc/httpd/conf.d/05-foreman-ssl.conf (4) Edit the Puppet Passenger application configuration file /etc/httpd/conf.d/25-puppet.conf These two files are managed by puppet within the Satellite/Capsule installer, so changes applied for performance tuning are lost when the satellite-installer is run to reconfigure or upgrade the Satellite. Manual re-application of the tuning and additional restart of the applications is required following an upgrade to ensure the tuning parameters are in place. Version-Release number of selected component (if applicable): Satellite/Capsule 6.2.z on RHEL7 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: After upgrade the tuning parameters are not in the place , it goes back to the default. Expected results: After upgrade the tuning parameters should be in place. Additional info:
Hi, Can I request to assign engineer for this Bugzilla please ? Selim Jahangir Technical Support Engineer Global Support Services Red Hat, Asia-Pacific"
These passenger settings are now the default. *** This bug has been marked as a duplicate of bug 1163452 ***
Just a comment about the duplication of this bug, this is largely solved by 1163452, as the new settings work for most workloads. For tuning in extremely large environments, you can make use of this which will ship in 6.2.8: https://bugzilla.redhat.com/show_bug.cgi?id=1305782#c14 The settings that would go in /etc/foreman-installer/custom-hiera.yaml would be something like this, depending on what you need to adjust: --- apache::mod::passenger::passenger_max_pool_size: 12 apache::mod::passenger::passenger_max_instances_per_app: 6 apache::mod::passenger::passenger_max_request_queue_size: 250 apache::mod::passenger::passenger_stat_throttle_rate: 120
Those changes in the custom-hiera.yaml will persist across installer runs.