Bug 900047 (JBPAPP6-1533)
Summary: | SystemMemoryUsageLoadMetric is not correct on Linux/Unix | ||
---|---|---|---|
Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Michal Karm Babacek <mbabacek> |
Component: | mod_cluster | Assignee: | Radoslav Husar <rhusar> |
Status: | CLOSED WONTFIX | QA Contact: | Michal Karm Babacek <mbabacek> |
Severity: | high | Docs Contact: | Russell Dickenson <rdickens> |
Priority: | high | ||
Version: | 6.0.0 | CC: | dimitris, lcosti, paul.ferraro, rhatlapa, rhusar, rsvoboda, smumford, twells |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
URL: | http://jira.jboss.org/jira/browse/JBPAPP6-1533 | ||
Whiteboard: | eap601candidate | ||
Fixed In Version: | Doc Type: | Known Issue | |
Doc Text: |
The `SystemMemoryUsageLoadMetric` does not show useful information on Linux or UNIX operating systems. For these systems, `HeapMemoryUsageLoadMetric` provides more useful information. The solution to this problem will be to change the algorithm of `SystemMemoryUsageLoadMetric` to subtract the `buffers/cache` value from the `used` number. The best method for doing this is under investigation.
|
Story Points: | --- |
Clone Of: | Environment: |
Linux/Unix operating systems with standard memory management
|
|
Last Closed: | 2013-11-25 19:24:41 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
Michal Karm Babacek
2012-03-14 14:51:04 UTC
Link: Added: This issue Cloned from MODCLUSTER-288 Security: Added: Public Docs QE Status: Added: NEW Labels: Added: eap6_need_triage Paul, can you take a look please? See comments for MODCLUSTER-288. As Paul said, please follow [MODCLUSTER-288]. This issue will likely result in a documentation task... Release Notes Docs Status: Added: Documented as Known Issue Release Notes Text: Added: The <code>SystemMemoryUsageLoadMetric</code> does not show useful information on Linux or UNIX operating systems. For these systems, <code>HeapMemoryUsageLoadMetric</code> provides more useful information. The solution to this probiem will be to change the algorithm of <code>SystemMemoryUsageLoadMetric</code> to subtract the <code>buffers/cache</code> value from the <code>used</code> number. The best method for doing this is under investigation. Affects: Added: Release Notes Labels: Removed: eap6_need_triage Added: eap601candidate Deferring to EAP 6.1/7 - the solution will probably involve dropping this metric altogether. Writer: Added: mistysj Release Notes Text: Removed: The <code>SystemMemoryUsageLoadMetric</code> does not show useful information on Linux or UNIX operating systems. For these systems, <code>HeapMemoryUsageLoadMetric</code> provides more useful information. The solution to this probiem will be to change the algorithm of <code>SystemMemoryUsageLoadMetric</code> to subtract the <code>buffers/cache</code> value from the <code>used</code> number. The best method for doing this is under investigation. Added: The `SystemMemoryUsageLoadMetric` does not show useful information on Linux or UNIX operating systems. For these systems, `HeapMemoryUsageLoadMetric` provides more useful information. The solution to this probiem will be to change the algorithm of `SystemMemoryUsageLoadMetric` to subtract the `buffers/cache` value from the `used` number. The best method for doing this is under investigation. Release Notes Text: Removed: The `SystemMemoryUsageLoadMetric` does not show useful information on Linux or UNIX operating systems. For these systems, `HeapMemoryUsageLoadMetric` provides more useful information. The solution to this probiem will be to change the algorithm of `SystemMemoryUsageLoadMetric` to subtract the `buffers/cache` value from the `used` number. The best method for doing this is under investigation. Added: The `SystemMemoryUsageLoadMetric` does not show useful information on Linux or UNIX operating systems. For these systems, `HeapMemoryUsageLoadMetric` provides more useful information. The solution to this problem will be to change the algorithm of `SystemMemoryUsageLoadMetric` to subtract the `buffers/cache` value from the `used` number. The best method for doing this is under investigation. Release Notes Docs Status: Removed: Documented as Known Issue Writer: Removed: mistysj Release Notes Text: Removed: The `SystemMemoryUsageLoadMetric` does not show useful information on Linux or UNIX operating systems. For these systems, `HeapMemoryUsageLoadMetric` provides more useful information. The solution to this problem will be to change the algorithm of `SystemMemoryUsageLoadMetric` to subtract the `buffers/cache` value from the `used` number. The best method for doing this is under investigation. Docs QE Status: Removed: NEW Guys, let's drop this feature. We came to the conclusion that without JNI, one can't do this properly from within the JDK quite some time ago... https://issues.jboss.org/browse/JBPAPP6-1533 Yeah, lets... This metric will be dropped starting from EAP 7. We shouldn't be dropping features in existing EAP. However, the concern is valid and we need to make sure that these limitations are documented in EAP 6 documentation so that users aren't let to believe this does something else. Michal please check this is properly documented in the documentation, not just part of old 'known issues' document for previous EAP releases (maybe a separate documentation Jira might be needed). In the current documentation, Administration Guide: mem The mem load metric uses free native memory as a load factor. Usage of this metric is discouraged because it provides a value that includes buffers and cache, so it is always a very low figure on every decent system with good memory management. So IMHO, Rado's concern is unfounded. Removed from EAP 6.4 beta release notes |