[ https://issues.apache.org/jira/browse/BOOKKEEPER-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067548#comment-13067548 ]
Flavio Junqueira commented on BOOKKEEPER-35: -------------------------------------------- It exists already, yes. If the client opens a ledger, then it will run the ledger recovery procedure automatically if the ledger hasn't been closed. On a side note, the whole deal with BOOKKEEPER-11 is due to some applications not wanting that automatic recovery. However, we designed BK from the beginning to have this feature and with BOOKKEEPER-11 we are proposing to extend the api so that applications may open a ledger without recovering it automatically. > 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