[ 
https://issues.apache.org/jira/browse/KAFKA-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jun Rao resolved KAFKA-474.
---------------------------

    Resolution: Fixed
      Assignee: David Arthur

Thanks for the patch. Committed to 0.8.
                
> 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
>            Assignee: David Arthur
>              Labels: bugs, newbie
>             Fix For: 0.8
>
>         Attachments: KAFKA-474.patch
>
>
> 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

Reply via email to