[
https://issues.apache.org/jira/browse/ACCUMULO-1770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13798369#comment-13798369
]
Eric Newton commented on ACCUMULO-1770:
---------------------------------------
OK, I've attached a graph comparing long runs with mmap'ing in glibc memory
allocator, and without. There's a little more memory usage in the mmap
version. Maybe over the course of a couple months this might add up to an
extra 16G, but I doubt it. The usage looks really flat.
> 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: comparing-glibc-settings.png, FragmentTest.java,
> FragmentTest.java, javamap.png, memory-usage.png, nativemap.png, no-mmap.png,
> three-day-tserver.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)
