[
https://issues.apache.org/jira/browse/KAFKA-474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13469333#comment-13469333
]
David Arthur commented on KAFKA-474:
------------------------------------
I took a look at AbstractFetcherManager and the broker -> thread map. I don't
see where/how this map is used to actually get the fetcher thread for a
particular broker. I see the fetcherSourceBroker method, but cannot find
anywhere where it is invoked.
In fact, the only usage of this map I can see is when fetcher threads are
created and removed.
Am I overlooking something?
> support changing host/port of a broker
> --------------------------------------
>
> Key: KAFKA-474
> URL: https://issues.apache.org/jira/browse/KAFKA-474
> Project: Kafka
> Issue Type: Bug
> Components: core
> Reporter: Jun Rao
> Labels: bugs, newbie
> Fix For: 0.8
>
>
> Currently, the consumer client caches the host/port of a broker and never
> refreshes the cache. This means that if a broker changes to a different host,
> the consumer client won't be able to connect to the new host without a
> restart. One possibility is to change AbstractFetcherManager to maintain a
> map of <Broker, fetcher>, instead of <broker id, fetcher>.
--
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
