[
https://issues.apache.org/jira/browse/BOOKKEEPER-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13258688#comment-13258688
]
Roger Bush commented on BOOKKEEPER-181:
---------------------------------------
Another point I think is useful is to think of this feature as not just
"scaling hedwig", but as the ability to dynamically choose many different kv
stores. I can see this has some importance for possible future uses of
BookKeeper. We already know, that with a tiny bit of ingenuity (already being
demonstrated by Hedwig), BookKeeper becomes a scalable, highly available record
logger.
Such a scalable, highly available logger is a very nice piece of technology,
which has many applications.
However, there are many applications where people will not trust any part of
their data to something they don't understand, like ZooKeeper. They would want
their metadata to be in something more conventional, like a (gasp) Oracle
database. In fact, storing important data in ZooKeeper might not even be
allowed by their compliance department. We could debate the extent to whether
this is a valid concern, but there are definitely lots of places that this
would kill the deal.
In this case, the Pluggable Metadata API comes to the rescue, allowing a simple
generic SQL adapter layer (someone else will write this) to work with all SQL
databases, thus making BK relevant in new places.
> 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
