[
https://issues.apache.org/jira/browse/BOOKKEEPER-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260347#comment-13260347
]
Flavio Junqueira commented on BOOKKEEPER-181:
---------------------------------------------
bq. one possible solution is using reference counting mechanism, each deleted
ledger should have a list of bookie who owed it. each bookie delete its
reference from the list when it finished garbage collecting that ledger. the
last one who deleted reference, delete the ledger item from table.
This is what I had in mind.
bq. even we have mechanism to remove items from delete table, but we still need
SCAN to get items from deleted ledgers table.
Agreed, I'm not saying that we don't need scans at all, but possibly we can do
it with more efficient scans.
> 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
