accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Park (JIRA)" <j...@apache.org>
Subject [jira] [Created] (ACCUMULO-3330) Tserver "Running low on memory" might be miscomputed
Date Thu, 13 Nov 2014 16:20:35 GMT
Jonathan Park created ACCUMULO-3330:
---------------------------------------

             Summary: Tserver "Running low on memory" might be miscomputed
                 Key: ACCUMULO-3330
                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3330
             Project: Accumulo
          Issue Type: Bug
            Reporter: Jonathan Park
            Priority: Minor


I'm not sure if this is JVM specific behavior, but I suspect the way we compute when to log
"Running low on memory" could be improved. 

Currently we use {{Runtime.getRuntime()}} and rely on the formula {{freeMemory() < maxMemory()
* 0.05}} to determine whether or not to log the warning. With Oracle's HotSpot VM, {{freeMemory()}}
appears to return the amount of free memory relative to the current JVM heap size (as returned
by {{totalMemory()}}. If {{totalMemory()}} != {{maxMemory()}} then this warning will start
appearing before I think it was intended to which is misleading.

Easiest workaround is to configure the JVM heap to have the min size = max size.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message