[
https://issues.apache.org/jira/browse/BOOKKEEPER-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266193#comment-13266193
]
Roger Bush commented on BOOKKEEPER-181:
---------------------------------------
@sijie - If you failed to delete it from a bookie, then it is still the
client's responsibility to call deleteLedger until it succeeds. Once it's
being deleted, it isn't going to be used anyway. You could always return an
exception that said it was partially deleted and can be retried (although I'm
not sure how this information would be used).
But at the end of the day, once the application decides it's not going to be
used, the ledger will be deleted until the delete succeeds. What is important
is the delete must be restartable.
So I'm wondering if this inconsistency matters, or if it's an inconsistent
state that doesn't matter.
> 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
