[ 
https://issues.apache.org/jira/browse/BOOKKEEPER-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485321#comment-13485321
 ] 

Yixue (Andrew) Zhu commented on BOOKKEEPER-362:
-----------------------------------------------

If we have millions of topic, then ZK probably will not be the right vehicle 
for the metadata. The storage (most SQL vendors) can have prefix compression, 
which makes the the serialized region list versus separate not much difference.

Even if we have cache (read-ahead/batching) in the storage layer, the API can 
still not expose it, the below-API layer can have cache tuned to the read-ahead.
This is the consideration of not using region-list in the API level.
It also makes the case of not exposing the <topic,region> in the region 
manager, as different store cache can optimize/organize it differently. 

I can see your points of reducing redundancy, but I think the flexibility out 
weight it.
Thoughts?
                
> Local subscriptions fail if remote region is down
> -------------------------------------------------
>
>                 Key: BOOKKEEPER-362
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-362
>             Project: Bookkeeper
>          Issue Type: Bug
>          Components: hedwig-server
>    Affects Versions: 4.2.0
>            Reporter: Aniruddha
>            Assignee: Yixue (Andrew) Zhu
>            Priority: Critical
>              Labels: hedwig
>             Fix For: 4.2.0
>
>         Attachments: rebase_remoteregion.patch, rebase_remoteregion.patch
>
>
> Currently, local subscriptions fail if the remote region hubs are down, even 
> if the local hub has subscribed to the remote topic previously. Because of 
> this, one region cannot function independent of the other. 
> A more detailed discussion related to this can be found here 
> http://mail-archives.apache.org/mod_mbox/zookeeper-bookkeeper-dev/201208.mbox/%3cCAOLhyDQSOF+Y+pvnyrd-HJRq1YEr=c8ok_b3_mr81r1g-9m...@mail.gmail.com%3e

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to