Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
The following settings are required to tune a Satellite 6 server for scale and are only available in custom-heira.yaml. We need to add these as options as installer flags if possible:
apache::mod::passenger::passenger_max_pool_size: 30
apache::mod::passenger::passenger_max_request_queue_size: 1000
apache::mod::passenger::passenger_max_requests: 1000
apache::mod::prefork::serverlimit: 1024
apache::mod::prefork::maxclients: 1024
apache::mod::prefork::maxrequestsperchild: 4000
qpid::open_file_limit: 65536
qpid::router::open_file_limit: 150100
candlepin::java_opts: "-Xms1024m -Xmx8192m"
postgresql::server::config_entries:
max_connections: 1000
shared_buffers: 4GB
work_mem: 4MB
checkpoint_segments: 32
checkpoint_completion_target: 0.9
effective_cache_size: 16GB
autovacuum_vacuum_cost_limit: 2000
log_min_duration_statement: 500
some of these may rely on changes being needed in the upstream puppet modules for Apache and Postgres, but as we work to provide better options for customers to *properly* tune their Satellite with our installer, we need to move these common used parameters out of custom-heira.yaml into proper flags + answer file locations.
See also:
https://bugzilla.redhat.com/show_bug.cgi?id=1692535
This issue has been successfully verified in 6.7 Snap10, now user can change the deployment size as per their requirement using satellite-installer.
# satellite-installer --help
--tuning INSTALLATION_SIZE Tune for an installation size. Choices: default, medium, large, extra-large, extra-extra-large (default: "default")
# satellite-installer --tuning medium --disable-system-checks
Installing Done [100%] [................................................................................................................................]
Success!
# grep tuning /etc/foreman-installer/scenarios.d/satellite.yaml
tuning: medium
:tuning: medium
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