[
https://issues.apache.org/jira/browse/BOOKKEEPER-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485044#comment-13485044
]
Yixue (Andrew) Zhu commented on BOOKKEEPER-362:
-----------------------------------------------
1) What I mean is that configuration can control which MetadataMgr to
construct, and in turn different RemoteSubMgr can be used. The NoOpRemoteSubMgr
makes perfect sense for Standalone usage. I am going to explicitly use it in
standalone case, similar with instantiateSubscriptionManager.
About the test case, I am explicitly testing the two implementation of
RemoteSubMgr, idempotent which MetadataMgr factory picks what RemoteSubMgr.
2) The ZKVersion used in the <topic,region> map is used to guard against the
case different hub-server use the map at the same time (or interleaved).
I do not expect # of regions will be in the magnitude that serialized
region-list would make much difference w.r.t. performance. I do not see why the
API would mandate the region-list to be returned.
The update to the ZK-node is to update/track the metadata version, to guard
against of different hubs trying to manipulate it.
On the region address versus region name. If the cfg.getRegions() returns a
data structure where (VIP/DNS-entry, region-name/alias), we could use the
name/alias. Current configuration does not have that information.
It is unlikely VIP/DNS-entry change, similar with changing region name.
We can open a separate tracking item if you feel strongly about it.
> 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
>
>
> 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
