You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Jonathan Park (JIRA)" <ji...@apache.org> on 2014/11/13 17:20:35 UTC
[jira] [Created] (ACCUMULO-3330) Tserver "Running low on memory"
might be miscomputed
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)