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 07:04:00 UTC
[jira] [Created] (BOOKKEEPER-35) Ability to force close a ledger
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
[jira] [Commented] (BOOKKEEPER-35) Ability to force close a ledger
Posted by "Flavio Junqueira (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Resolved] (BOOKKEEPER-35) Ability to force close a ledger
Posted by "dhruba borthakur (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (BOOKKEEPER-35) Ability to force close a ledger
Posted by "dhruba borthakur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BOOKKEEPER-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067542#comment-13067542 ]
dhruba borthakur commented on BOOKKEEPER-35:
--------------------------------------------
Hi Flavio, sounds right. Does this feature already exist?
> 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
[jira] [Commented] (BOOKKEEPER-35) Ability to force close a ledger
Posted by "dhruba borthakur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BOOKKEEPER-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067551#comment-13067551 ]
dhruba borthakur commented on BOOKKEEPER-35:
--------------------------------------------
Got it, I am closing this one.
> 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
[jira] [Commented] (BOOKKEEPER-35) Ability to force close a ledger
Posted by "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