[
https://issues.apache.org/jira/browse/KAFKA-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14059203#comment-14059203
]
nicu marasoiu commented on KAFKA-1535:
--------------------------------------
So what I understand from the issue: the topic metadata responded includes only
the brokers holding active or passive replicas of some partitions from the
topic.
The task want to list all the available brokers, just in case other brokers get
assigned partitions / shards from the topic.
This would be a safety measure (if all the currently assigned brokers go down),
as well as a performance measure (client to pick up quickly new assigns without
stressing too much the current brokers assignees).
Sorry if I am innacurrate, I am not brushed up with kafka yet.
> 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
>
> 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)
