[
https://issues.apache.org/jira/browse/BOOKKEEPER-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260346#comment-13260346
]
Sijie Guo commented on BOOKKEEPER-181:
--------------------------------------
> Regarding the sync/async thing, we have two options here.
I would prefer options 1, in metastore layer. BookKeeper & Hedwig should use
async calls to talk with metastore, which make implementing metastore-based
ledger manager & topic manager much easier. From my previous work, I use
asynchbase library which provides async calls.
BTW, I am not sure a versioned api is enough for hedwig leader election. Maybe
we need a CAS method for it. so I would suggest that it would better to provide
the ledger election algorithm using the proposal api.
> 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
