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

["Ivan Kelly (JIRA)" <ji...@apache.org>]

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

Ivan Kelly commented on BOOKKEEPER-594:
---------------------------------------

This should go into the next release, as it's part of making bookkeeper availability independent of zookeeper sessions.

> 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.4.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)