accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-1708) Error during minor compaction left tserver in bad state
Date Tue, 07 Jan 2014 23:55:51 GMT


Josh Elser commented on ACCUMULO-1708:

[~kturner] is this still something you are wanting to try to get into 1.6.0? I remember being
pointed to some pages which strongly recommended against catching Error. With the introduction

{noformat}-XX:OnOutOfMemoryError="${ACCUMULO_KILL_CMD:-kill -9 %p}"{noformat}
in {{bin/accumulo}} and the ability for users to define their own {{ACCUMULO_KILL_CMD}} in
{{}}, is this even as big of a worry as previously?

> Error during minor compaction left tserver in bad state
> -------------------------------------------------------
>                 Key: ACCUMULO-1708
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>    Affects Versions: 1.4.0
>            Reporter: Keith Turner
>            Priority: Critical
>             Fix For: 1.6.0
>         Attachments:
> 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

View raw message