[
https://issues.jboss.org/browse/MODCLUSTER-157?page=com.atlassian.jira.pl...
]
Michal Babacek closed MODCLUSTER-157.
-------------------------------------
Closing. Clean-up.
At least one of the following applies:
* the issue has been thoroughly tested as a part of one of the current releases
or
* it hasn't occurred in ~2 years
or
* it's utterly harmless
SystemMemoryUsageLoadMetric returns wrong load metric
-----------------------------------------------------
Key: MODCLUSTER-157
URL:
https://issues.jboss.org/browse/MODCLUSTER-157
Project: mod_cluster
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 1.0.3.GA, 1.1.0.CR2
Reporter: Masafumi Miura
Assignee: Paul Ferraro
Fix For: 1.0.4.GA, 1.1.0.CR3
When using SystemMemoryUsageLoadMetric, mod_cluster prioritizes dispatching requests to a
machine which are using system memory higher than other machines. This loadbalancing
behaviour is odd.
SystemMemoryUsageLoadMetric[1] returns wrong load metric. The
SystemMemoryUsageLoadMetric#getLoad() should not return "free / total". It
should return "(total - free) / total" (= usage / total ) like
HeapMemoryUsageLoadMetric[2].
[1]
http://anonsvn.jboss.org/repos/mod_cluster/tags/1.0.3.GA/src/main/java/or...
[2]
http://anonsvn.jboss.org/repos/mod_cluster/tags/1.0.3.GA/src/main/java/or...
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)