accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Vines (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-1708) Error during minor compaction left tserver in bad state
Date Sat, 26 Oct 2013 00:22:30 GMT

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

John Vines commented on ACCUMULO-1708:
--------------------------------------

So it sounds like your ThreadGroup approach is a partial solution, but it's the best we got
so far. Do we see an overall fix including this approach? If so, I think we should go ahead
and see about making this change and document the possibilities that can then occur for future
tickets.

> Error during minor compaction left tserver in bad state
> -------------------------------------------------------
>
>                 Key: ACCUMULO-1708
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1708
>             Project: Accumulo
>          Issue Type: Bug
>    Affects Versions: 1.4.0
>            Reporter: Keith Turner
>            Priority: Critical
>             Fix For: 1.6.0
>
>         Attachments: ThreadTest.java
>
>
> A tserver experienced a OOME during minor compaction.  This OOME was thrown because java
could not create a native thread.  Minor compactions only catch declared exceptions and RuntimeExceptions.
 This left the system in a state where the compaction was not running but the tserver thought
it was.  This cause"flush -w" to hang and prevented the tserver from reclaiming memory.
> For whatever reason the OOME handler that kills the process did not kick in (seems it
only kicks in w/ OOME related to heap allocation).



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message