[
https://issues.apache.org/jira/browse/KAFKA-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao reassigned KAFKA-1535:
------------------------------
Assignee: nicu marasoiu (was: Jay Kreps)
Nicu,
Yes, your observation is correct. The way that we update liveBrokers in
MetadataCache.updateCache() doesn't seem right. We only add newly received live
brokers to the list. However, there could be existing brokers in that list that
are now dead. Those dead brokers shouldn't be returned to the clients. We
should probably just take the new live broker list and cache it. Do you want to
do a followup patch in this jira?
> return all live brokers in TopicMetadataResponse
> ------------------------------------------------
>
> Key: KAFKA-1535
> URL: https://issues.apache.org/jira/browse/KAFKA-1535
> Project: Kafka
> Issue Type: Improvement
> Components: core
> Affects Versions: 0.8.2
> Reporter: Jun Rao
> Assignee: nicu marasoiu
> Labels: newbie
> Attachments:
> KAFKA-1535__return_all_live_brokers_in_TopicMetadataResponse_.patch
>
>
> Currently, we only return the brokers that have assigned replicas for a topic
> in TopicMetadataResponse. The new producer will use those brokers for
> refreshing metadata. Now suppose that we stop all those brokers, copy all
> local data to some new hosts and then restart those hosts (with the original
> broker id). There is no way for the new producer to automatically get the
> information about the new brokers since all old brokers are gone.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
