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.

Bug 2215110

Summary: [RFE] Add a flag to set the heap size (Xms and Xmx) for tomcat. At this moment, there is an option only for puppetserver
Product: Red Hat Satellite Reporter: Waldirio M Pinheiro <wpinheir>
Component: InstallationAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED MIGRATED QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.14.0CC: egolov, ehelms, thadzhie
Target Milestone: UnspecifiedKeywords: FutureFeature, MigratedToJIRA
Target Release: Unused   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-06-06 16:22:12 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Waldirio M Pinheiro 2023-06-14 18:27:30 UTC 
Description of problem:
Add a flag to set the heap size (Xms and Xmx) for tomcat. At this moment, there is an option only for puppetserver

Version-Release number of selected component (if applicable):
all of them

How reproducible:
100%

Steps to Reproduce:
1. install satellite, the default Xmx and Xms is 2GiB
2. If you need to change the heap size for tomcat, you need to add it via custom-hiera
3.

Actual results:
Only via custom hiera

Expected results:
Flag via satellite-installer that will set the heap size for tomcat

Additional info:
Comment 2 Eric Helms 2023-07-18 18:12:11 UTC 
Can you expand on why you need this? What issues are being run into, and/or what scenarios lead to needing to modify this value?
Comment 3 Waldirio M Pinheiro 2023-08-04 19:43:37 UTC 
Hello,

Sure, eventually, we have customers with a huge number of content hosts that will cause a huge # of calls to candlepin, when doing operations related to subscriptions. That said, the standard of 2GiB it's not enough and as consequence, CP just died with "out of memory".

In order to fix that, we bump the "heap size" used by the java vm. Below, we can see an entry from custom-hiera

---
...
candlepin::java_opts: "-Xms1024m -Xmx8192m"
...
---

This will change from 2G to 8G, avoiding the issue mentioned above.

At this moment, there is no flag to change this configuration via satellite-installer, only via custom-hiera as presented above.

Thank you!

Please, let me know if you have additional questions or concerns.
Waldirio
Comment 4 Eric Helms 2024-06-06 16:22:12 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Comment 5 Red Hat Bugzilla 2024-10-05 04:26:18 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days