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

Posted to dev@bookkeeper.apache.org by "Flavio Junqueira (JIRA)" <ji...@apache.org> on 2013/08/27 23:17:52 UTC

[jira] [Commented] (BOOKKEEPER-443) Revisit Ledger Deletion in BookKeeper

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

Flavio Junqueira commented on BOOKKEEPER-443:
---------------------------------------------

This jira discusses the semantics of deletes while my understanding of BOOKKEEPER-464 is that it changes/improves the GC mechanism. Does it make sense to keep this jira or should we move the discussion completely to BOOKKEEPER-464?
                
> Revisit Ledger Deletion in BookKeeper
> -------------------------------------
>
>                 Key: BOOKKEEPER-443
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-443
>             Project: Bookkeeper
>          Issue Type: Improvement
>          Components: bookkeeper-server
>            Reporter: Jiannan Wang
>             Fix For: 4.3.0
>
>
> Currently, we don't look at ledger metadata when delete ledgers. So when a client is opening/writing a ledger and other client delete it, the behavior is undefined.
> So we would suggest if a client is writing/recovery a ledger, we should not delete it. We can change the behavior of ledger deletion to perform a conditional remove only when the state of ledger is CLOSED.

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