You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Keith Turner (JIRA)" <ji...@apache.org> on 2013/09/11 16:11:52 UTC
[jira] [Commented] (ACCUMULO-1708) Error during minor compaction
left tserver in bad state
[ https://issues.apache.org/jira/browse/ACCUMULO-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13764334#comment-13764334 ]
Keith Turner commented on ACCUMULO-1708:
----------------------------------------
I propose catching Error (OutOfMemoryException extends this) in minor compaction and halting the process. I am thinking this may be a good patch for 1.4.5, 1.5.1, and 1.6.0. A more general fix may be to make all server threads catch Error and halt the process, could do this for 1.6. Thoughts?
> 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
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira