accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Turner (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-1770) out of memory error on very long running tablet server
Date Fri, 11 Oct 2013 15:44:43 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-1770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13792731#comment-13792731
] 

Keith Turner commented on ACCUMULO-1770:
----------------------------------------

bq.  Each run ingested about 3.8G of value data.

What was the memory map size setting in Accumulo?  How many times did it minor compact?

> 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, memory-usage.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)

Mime
View raw message