[jira] [Commented] (BOOKKEEPER-35) Ability to force close a ledger

["Flavio Junqueira (JIRA)" <ji...@apache.org>]

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

Flavio Junqueira commented on BOOKKEEPER-35:
--------------------------------------------

When a client opens a ledger for reading (it is not the writer of the ledger), if it can't find a "closed" znode on ZooKeeper for that ledger, then it executes a recovery procedure to close the ledger. I believe this is the feature you're looking for, yes?

> Ability to force close a ledger
> -------------------------------
>
>                 Key: BOOKKEEPER-35
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-35
>             Project: Bookkeeper
>          Issue Type: Improvement
>          Components: bookkeeper-client, bookkeeper-server
>            Reporter: dhruba borthakur
>
> We need the ability to make a bookkeeper client force-close a ledger that has been opened (and being written to) by another client. Is that currenly possible?
> When a  HDFS namenode failover occurs, the standby namenode would like to ensure that the primary namenode cannot write to the transaction log any more. The standby namenode would first invoke this new bookkeeper API before making himself the primary.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira