[
https://issues.apache.org/jira/browse/BOOKKEEPER-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13262519#comment-13262519
]
Sijie Guo commented on BOOKKEEPER-181:
--------------------------------------
Thanks Matteo providing such interesting idea to improve garbage collection.
Just has one concern about this solution, it may introduce inconsistency
between those deleted ledgers which might make deleteLedger confusing.
for example, ledger l has bookie list (bk1, bk2, bk3). application called
deleteLedger(l), it added l to bk1's deleted ledger list, but failed to add l
to bk2's deleted ledger list. then application receive an exception, which
means the deletion failed.
if application doesn't deleteLedger(l) again, which means ledger l is not
deleted. but the data of ledger l on bk1 might be garbage collected, which
might cause data loss.
> Scale hedwig
> ------------
>
> Key: BOOKKEEPER-181
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-181
> Project: Bookkeeper
> Issue Type: Improvement
> Components: bookkeeper-server, hedwig-server
> Reporter: Sijie Guo
> Assignee: Sijie Guo
> Fix For: 4.2.0
>
> Attachments: hedwigscale.pdf, hedwigscale.pdf
>
>
> Current implementation of Hedwig and BookKeeper is designed to scale to
> hundreds of thousands of topics, but now we are looking at scaling them to
> tens to hundreds of millions of topics, using a scalable key/value store such
> as HBase.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
