[
https://issues.apache.org/jira/browse/BOOKKEEPER-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505487#comment-13505487
]
Flavio Junqueira commented on BOOKKEEPER-464:
---------------------------------------------
Unless I'm misunderstanding the meaning of zombie entries, the operations
related to a ledger fragment in any given bookie need to be atomic. If a bookie
starts replicating a ledger fragment because it has been added to the ensemble
of ledger but it doesn't complete the replication process because, e.g., its
disk becomes full, then we remove the partially replicated ledger fragment. If
a bookie is notified that a ledger has been marked for deletion while it is
replicating the ledger fragment, then it shouldn't delete the ledger fragment
in the middle of the replication process.
Perhaps we should have a sequencer thread in each bookie that enforces
atomicity in the way I'm mentioning.
> Provide an improved GC algorithm
> --------------------------------
>
> Key: BOOKKEEPER-464
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-464
> Project: Bookkeeper
> Issue Type: Sub-task
> Components: bookkeeper-server
> Reporter: Sijie Guo
> Assignee: Fangmin Lv
> Fix For: 4.3.0
>
> Attachments: BOOKKEEPER-464.patch
>
>
--
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
