You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@bookkeeper.apache.org by "Ivan Kelly (JIRA)" <ji...@apache.org> on 2014/02/04 17:54:15 UTC

[jira] [Updated] (BOOKKEEPER-729) Bookie shouldn't exit with 0, if exiting from deathwatcher and thread death was caused by OOM

     [ https://issues.apache.org/jira/browse/BOOKKEEPER-729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ivan Kelly updated BOOKKEEPER-729:
----------------------------------

    Attachment: 0005-BOOKKEEPER-729-When-bookie-exits-with-an-error-and-c.patch

> Bookie shouldn't exit with 0, if exiting from deathwatcher and thread death was caused by OOM
> ---------------------------------------------------------------------------------------------
>
>                 Key: BOOKKEEPER-729
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-729
>             Project: Bookkeeper
>          Issue Type: Bug
>            Reporter: Ivan Kelly
>            Assignee: Ivan Kelly
>             Fix For: 4.3.0
>
>         Attachments: 0005-BOOKKEEPER-729-When-bookie-exits-with-an-error-and-c.patch
>
>
> I've seen the deathwatcher reset the exit code to 0, even after it was set correct. We should make setting the exitcode a one way operation. 



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)