You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "Fangmin Lv (JIRA)" <ji...@apache.org> on 2013/01/05 15:46:12 UTC

[jira] [Updated] (BOOKKEEPER-192) Hub server should try to close ledgers when releasing topic or shutting down server

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

Fangmin Lv updated BOOKKEEPER-192:
----------------------------------

    Attachment: BOOKKEEPER-192.patch

Attach a patch:
1. close ledgers when releasing topic and shutting down server.
2. change fenced read log level from error to warn and add a new metric about fenced read. 
                
> Hub server should try to close ledgers when releasing topic or shutting down server
> -----------------------------------------------------------------------------------
>
>                 Key: BOOKKEEPER-192
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-192
>             Project: Bookkeeper
>          Issue Type: Sub-task
>            Reporter: Sijie Guo
>         Attachments: BOOKKEEPER-192.patch
>
>
> currently, hub server doesn't close ledgers when releasing topic ownership or shutting down server. so the ledgers need to be recovered when the topic is acquired again, which introduce latency to acquire topic.

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