[
https://issues.apache.org/jira/browse/BOOKKEEPER-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aniruddha resolved BOOKKEEPER-261.
----------------------------------
Resolution: Duplicate
Marked this as a duplicate. See
https://issues.apache.org/jira/browse/BOOKKEEPER-323
> Let a hedwig-client discover the region of the hedwig-server cluster it is
> connected to
> ---------------------------------------------------------------------------------------
>
> Key: BOOKKEEPER-261
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-261
> Project: Bookkeeper
> Issue Type: Improvement
> Components: hedwig-client
> Reporter: Aniruddha
> Assignee: Aniruddha
> Priority: Minor
> Attachments: BK-261.patch
>
>
> Currently, the client-server protocol doesn't let a Hedwig client discover
> the region that it is a part of. There are a couple of approaches that I
> could think of to do this - 1) The client publishes and subscribes to a
> randomly generated topic-name. It can then set it's region to the srcRegion
> of the received message. 2) Have a discovery operation akin to the
> publish/subscribe operations and let the server respond to this with
> information about itself (region name and any other information it might want
> to pass on to the client). I personally prefer (2). I could produce a patch
> if the approach looks good.
--
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
