[
https://issues.apache.org/jira/browse/BOOKKEEPER-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13457127#comment-13457127
]
Aniruddha commented on BOOKKEEPER-407:
--------------------------------------
[~hustlmsp]
There are a couple of other scenarios where this problem will occur.
1) The client is only a publisher. Since the publish channel is multiplexed at
the moment, the channel is not(should not be) disconnected in case of topic
movement. The client will never clear the topic2Host entry even if the topic
moves.
2) The client sends a publish request. Publish succeeds. Topic moves, and the
subscription channel for that topic gets disconnected, so the topic2Host
mapping is cleared. Now the client gets a response for the publish request from
the old server and this results in an entry being made in the topic2Host map.
I believe that it is safe (and necessary) to always do a put() there. What do
you think?
> Hedwig client doesn't remove old topic2Host mapping in case of redirect
> -----------------------------------------------------------------------
>
> Key: BOOKKEEPER-407
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-407
> Project: Bookkeeper
> Issue Type: Bug
> Affects Versions: 4.2.0
> Reporter: Aniruddha
>
> In the storeTopic2HostMapping function, there is a topic2Host.putIfAbsent().
> This doesn't seem correct as we should always update the mapping in case of a
> redirect.
--
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
