accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "marco polo (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-1708) Error during minor compaction left tserver in bad state
Date Tue, 15 Sep 2015 12:49:46 GMT

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

marco polo commented on ACCUMULO-1708:
--------------------------------------

Perhaps it might behoove us to centralize some of this error handling in an uncaught exception
handler so that we can exit when we see fit. I'm not sure It's prudent to immediate exit on
an OutOfMemoryError, but we could detect from the MemoryMXBean bean our memory state and make
determinations on how to clean up. 

And when I say, "us" I mean you. 

I'm kidding. When I mean you, I actually mean Josh. 

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

Mime
View raw message