You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@bookkeeper.apache.org by "dhruba borthakur (JIRA)" <ji...@apache.org> on 2011/07/19 09:25:57 UTC

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

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

dhruba borthakur resolved BOOKKEEPER-35.
----------------------------------------

    Resolution: Not A Problem

This API already exists.

> 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