accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (ACCUMULO-3330) Tserver "Running low on memory" appears more frequently than necessary when min heap != max heap
Date Wed, 27 May 2015 19:24:21 GMT

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

Christopher Tubbs reopened ACCUMULO-3330:
-----------------------------------------

This is not a duplicate of ACCUMULO-3322. That issue is about the frequency of the gc debug
messages.

This one is about the frequency of the "Running low on memory" warning.

> 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
(v6.3.4#6332)

Mime
View raw message