[
https://issues.apache.org/jira/browse/BOOKKEEPER-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13496945#comment-13496945
]
Sijie Guo commented on BOOKKEEPER-249:
--------------------------------------
Thanks Rakesh for comments.
{quote}
just add one more step in autorereplication logic to update these failed
bookie's ledgers in 'ledgers/deleted/Bi/'.
{quote}
It was a good idea to resolve zombie entry issue when changing ensembles. We
could first add the failed bookie to '/ledgers/deleted/Bi', then update the
ledger metadata to use new ensemble. just one point that bookie needs to take
care, it should not garbage collect those ledgers still not marked as DELETED.
{quote}
using zk multi-transaction apis
{quote}
In general, we could not use multi-transaction. As in BOOKKEEPER-181, ledger
metadata might be stored in other metadata storage. so the key point is that we
should only update ledger metadata after updating failed bookie's ledgers in
'/ledgers/deleted/Bi' when changing ensemble.
> Revisit garbage collection algorithm in Bookie server
> -----------------------------------------------------
>
> Key: BOOKKEEPER-249
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-249
> Project: Bookkeeper
> Issue Type: Improvement
> Components: bookkeeper-server
> Reporter: Sijie Guo
> Fix For: 4.2.0
>
> Attachments: gc_revisit.pdf
>
>
> Per discussion in BOOKKEEPER-181, it would be better to revisit garbage
> collection algorithm in bookie server. so create a subtask to focus on it.
--
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
