You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "Sijie Guo (JIRA)" <ji...@apache.org> on 2012/12/17 06:26:12 UTC

[jira] [Resolved] (BOOKKEEPER-313) Bookkeeper shutdown call from Bookie thread is not shutting down server

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

Sijie Guo resolved BOOKKEEPER-313.
----------------------------------

    Resolution: Won't Fix
    
> Bookkeeper shutdown call from Bookie thread is not shutting down server
> -----------------------------------------------------------------------
>
>                 Key: BOOKKEEPER-313
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-313
>             Project: Bookkeeper
>          Issue Type: Bug
>          Components: bookkeeper-server
>    Affects Versions: 4.1.0, 4.2.0
>            Reporter: Vinay
>
> shutdown(..) call from inside Bookie#run() is not shutting down the server.
> Bookie thread is waiting to join itself.
> Shutdown called from here
> {code} if (!shuttingdown) {
>             // some error found in journal thread and it quits
>             // following add operations to it would hang unit client timeout
>             // so we should let bookie server exists
>             LOG.error("Journal manager quits unexpectedly.");
>             shutdown(ExitCode.BOOKIE_EXCEPTION);
>         }{code}
> bookie thread is waiting at *this.join()* in below code
> {code}// Shutdown the ZK client
>                 if(zk != null) zk.close();
>                 // Shutdown journal
>                 journal.shutdown();
>                 this.join();
>                 syncThread.shutdown();
>                 // close Ledger Manager{code}

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