[mod_cluster-issues] [JBoss JIRA] Updated: (MODCLUSTER-157) SystemMemoryUsageLoadMetric returns wrong load metric

Paul Ferraro (JIRA) jira-events at lists.jboss.org
Thu May 13 11:25:26 EDT 2010


     [ https://jira.jboss.org/jira/browse/MODCLUSTER-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Ferraro updated MODCLUSTER-157:
------------------------------------

        Fix Version/s: 1.1.0.CR3
    Affects Version/s: 1.1.0.CR2
                           (was: 1.0.2.GA)


> SystemMemoryUsageLoadMetric returns wrong load metric
> -----------------------------------------------------
>
>                 Key: MODCLUSTER-157
>                 URL: https://jira.jboss.org/jira/browse/MODCLUSTER-157
>             Project: mod_cluster
>          Issue Type: Bug
>    Affects Versions: 1.0.3.GA, 1.1.0.CR2
>            Reporter: Masafumi Miura
>            Assignee: Jean-Frederic Clere
>             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/org/jboss/modcluster/load/metric/impl/SystemMemoryUsageLoadMetric.java
> [2] http://anonsvn.jboss.org/repos/mod_cluster/tags/1.0.3.GA/src/main/java/org/jboss/modcluster/load/metric/impl/HeapMemoryUsageLoadMetric.java

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the mod_cluster-issues mailing list