[
https://issues.apache.org/jira/browse/KAFKA-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14065435#comment-14065435
]
nicu marasoiu commented on KAFKA-1535:
--------------------------------------
the other strange thing: in the metadataCache.aliveBrokers it looks like all
the time (at any update), the new set of alive brokers are added (put) there.
This means that old brokers still linger there indefinitely. Is this intended
like this, for the clients to get even long dead brokers, just in case they may
get back sometime?
The correct thing would be for me to delete the old brokers (to completely
reset the aliveBrokers, not to keep adding to the existing mutable map)
> 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
> 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)
