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 2013/03/26 19:27:20 UTC

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

Ivan Kelly created BOOKKEEPER-594:
-------------------------------------

             Summary: AutoRecovery shutting down on SyncDisconnected
                 Key: BOOKKEEPER-594
                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-594
             Project: Bookkeeper
          Issue Type: Bug
            Reporter: Ivan Kelly
            Assignee: Ivan Kelly
            Priority: Critical
             Fix For: 4.3.0


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 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