[
https://issues.apache.org/jira/browse/ACCUMULO-1770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13793908#comment-13793908
]
Josh Elser commented on ACCUMULO-1770:
--------------------------------------
I started poking through
http://www.oracle.com/technetwork/java/javase/memleaks-137499.html#gbyvk
Not sure if you've been there yourself yet, but it looks like some good
suggestions on debugging native allocations.
> out of memory error on very long running tablet server
> ------------------------------------------------------
>
> Key: ACCUMULO-1770
> URL: https://issues.apache.org/jira/browse/ACCUMULO-1770
> Project: Accumulo
> Issue Type: Bug
> Components: tserver
> Reporter: Eric Newton
> Assignee: Eric Newton
> Attachments: FragmentTest.java, javamap.png, memory-usage.png,
> nativemap.png
>
>
> On a large cluster it was noticed that a few of the tablet servers had been
> pushed into swap. This didn't effect the performance of the server until it
> ran out of memory, and the process was killed. The gc reports in the debug
> log showed the system had plenty of heap space for the JVM. The number of
> threads in the server were not excessive (dozens). This cluster ingests some
> large values (megabytes). The tablet server had been up for a month prior to
> running out of memory. MALLOC_ARENA_MAX had already been set to 1.
> * Investigate the effect of fragmentation on memory usage for large value
> inserts.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
