[jira] [Resolved] (ACCUMULO-3330) Tserver "Running low on memory" appears more frequently than necessary when min heap != max heap

["Christopher Tubbs (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ACCUMULO-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christopher Tubbs resolved ACCUMULO-3330.
-----------------------------------------
    Resolution: Not A Problem

I think the behavior is intended. I think it's still a useful signal to see that the free memory is low, relative to the current heap size, as that can have an impact on performance. We don't only care that the memory is low relative to the max. So, I think this is fine. If there is a still a change desired here, then please file a new issue or PR at https://github.com/apache/accumulo

> Tserver "Running low on memory" appears more frequently than necessary when min heap != max heap
> ------------------------------------------------------------------------------------------------
>
>                 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
(v8.3.4#803005)