[
https://issues.apache.org/jira/browse/KAFKA-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14062214#comment-14062214
]
Jay Kreps commented on KAFKA-1535:
----------------------------------
Yeah we do all development on trunk and just cut branches as a stable point for
critical point fixes needed after the release.
> 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)
