You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "Flavio Junqueira (JIRA)" <ji...@apache.org> on 2014/03/25 00:34:44 UTC

[jira] [Commented] (BOOKKEEPER-594) AutoRecovery shutting down on SyncDisconnected

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

Flavio Junqueira commented on BOOKKEEPER-594:
---------------------------------------------

What's the status of this jira? It has a single sub-task resolved, but it has a patch attached and the status is open.

> AutoRecovery shutting down on SyncDisconnected
> ----------------------------------------------
>
>                 Key: BOOKKEEPER-594
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-594
>             Project: Bookkeeper
>          Issue Type: Bug
>          Components: bookkeeper-auto-recovery
>            Reporter: Ivan Kelly
>            Assignee: Ivan Kelly
>            Priority: Critical
>             Fix For: 4.3.0
>
>         Attachments: BOOKKEEPER-594.diff
>
>
> Currently the AutoRecovery daemon will shut down on SyncDisconnected. This is the wrong behaviour. It should wait until it gets a expired signal before shutting down. If autoRecoveryDaemonEnabled=true, then the autorecovery deamon is running in the same process as the bookie, the bookie death watcher will take down the bookie at this point also, but as the bookie hasn't shutdown, exit code will be 0, which is confusing to any monitoring app.



--
This message was sent by Atlassian JIRA
(v6.2#6252)