[
https://issues.apache.org/jira/browse/BOOKKEEPER-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13271396#comment-13271396
]
Sijie Guo commented on BOOKKEEPER-181:
--------------------------------------
@Flavio, I know that CAS could do it by retrying when failure happened. but if
a metastore has auto-increment support, why not use it? if a metastore doens't
support auto-increment, we could fall back to use CAS.
> I'm not entirely convinced that the identification of ledgers should be
> delegated to the metadata store.
yes. we don't need to delegate to metastore. just what
HierarchicalLedgerManager did, we could still using zookeeper as id generator.
Also, introducing counter per namespace is very awesome. I like the idea.
> 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
