Bug 535398 (RHQ-2099)
Summary: | be able to customize the launcher scripts' memory settings but leave the rest of the defaults | ||
---|---|---|---|
Product: | [Other] RHQ Project | Reporter: | John Mazzitelli <mazz> |
Component: | Launch Scripts | Assignee: | John Mazzitelli <mazz> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | unspecified | CC: | cwelton, jshaughn |
Target Milestone: | --- | Keywords: | FutureFeature, Improvement |
Target Release: | --- | ||
Hardware: | All | ||
OS: | All | ||
URL: | http://jira.rhq-project.org/browse/RHQ-2099 | ||
Whiteboard: | |||
Fixed In Version: | 1.4 | Doc Type: | Enhancement |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-05-05 20:53:28 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: |
Description
John Mazzitelli
2009-05-20 13:53:00 UTC
We might want to consider further splitting it out and having separate env vars for heap and permgen, e.g.: RHQ_SERVER_INITIAL_HEAP_SIZE RHQ_SERVER_MAX_HEAP_SIZE RHQ_SERVER_INITIAL_PERMGEN_SIZE RHQ_SERVER_MAX_PERMGEN_SIZE or: RHQ_SERVER_HEAP_SIZE_OPTS RHQ_SERVER_PERMGEN_SIZE_OPTS Otherwise, users could easily neglect to specify permgen setting, e.g.: RHQ_SERVER_MEMORY_JAVA_OPTS=-Xms2048m -Xmx2048m and end up with the JVM max permgen default of 64MB, which is too low for the JON Server, which needs a minimum of around 128MB. I dont like the sound of RHQ_SERVER_*special_property*_JAVA_OPTS. We should have some sort of .env file the server sources in order to pick up its JAVA_OPTS. The people can override this easily: either a) just edit the .env directly to add/change the options or b) override the value in the .env file by specifying an environment variable. This is easy to do because the user just copies the current value of the property from the .env file, tweaks it and specifies the new value as an env. var. Setting this to critical since its impacting customers running 1.2, e.g. case 295891 We need to NOT expose INITIAL heap. In fact I say we just have "RHQ_AGENT_HEAP_SIZE" and we automatically set the initial and max to that value. Greg and Charles can tell you why :) Customer was fine starting the server, but once it needed to process alot of agents, heap grew and the max was too much for the memory the box had. This kind of problem would have been detected much early on if initial and max were the same. Sorry - I mean RHQ_SERVER_HEAPSIZE (not agent). Moving features/improvements to 1.4 This bug was previously known as http://jira.rhq-project.org/browse/RHQ-2099 mass add of key word FutureFeature to help track Charles and Mazz, what do we want to do here? this is low priority/severity at minimum. I'm not too excited about this one - wouldn't hurt my feelings if we just closed this. I don't think its very important. The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |