[
https://issues.apache.org/jira/browse/KAFKA-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13850081#comment-13850081
]
Guozhang Wang commented on KAFKA-1181:
--------------------------------------
If the broker list is set to be fixed and may not match any existing broker id,
should we just remove its broker id field just to avoid being confused with
debug info?
> Consolidate brokerList and topicPartitionInfo in BrokerPartitionInfo
> --------------------------------------------------------------------
>
> Key: KAFKA-1181
> URL: https://issues.apache.org/jira/browse/KAFKA-1181
> Project: Kafka
> Issue Type: Bug
> Reporter: Guozhang Wang
> Assignee: Guozhang Wang
>
> brokerList in BrokerConfig is used to send the TopicMetadataRequest to known
> brokers, and the broker id always starts at 0 and increase incrementally, AND
> it is never updated in BrokerPartitionInfo even after the topic metadata
> response has been received.
> The real broker ids info is actually stored in topicPartitionInfo:
> HashMap[String, TopicMetadata]. Which is refreshed with topic metadata
> response. Therefore we could see different broker ids from logging entris
> reporting failues of metadata request and failures of produce requests.
> The solution here is to consolidate these two, reading the initial broker
> list but keep it refreshed with topic metadata responses.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
