[
https://issues.apache.org/jira/browse/KAFKA-5463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-5463.
--------------------------------
Resolution: Fixed
Fix Version/s: 0.11.0.0
Issue resolved by pull request 3358
[https://github.com/apache/kafka/pull/3358]
> Controller incorrectly logs rack information when new brokers are added
> -----------------------------------------------------------------------
>
> Key: KAFKA-5463
> URL: https://issues.apache.org/jira/browse/KAFKA-5463
> Project: Kafka
> Issue Type: Bug
> Components: config, controller
> Affects Versions: 0.10.2.0, 0.11.0.0, 0.10.2.1
> Environment: Ubuntu Trusty (14.04.5), Oracle JDK 8
> Reporter: Jeff Chao
> Priority: Minor
> Fix For: 0.11.0.0
>
>
> When a new broker is added, on an {{UpdateMetadata request}}, rack
> information won't be present in the state-change log even if configured.
> Example:
> {{pri=TRACE t=Controller-1-to-broker-0-send-thread at=logger Controller 1
> epoch 1 received response {error_code=0} for a request sent to broker
> <ip>:<port> (id: 0 rack: null)}}
> This happens because {{ControllerChannelManager}} always instantiates a
> {{Node}} using the same constructor whether or not rack-aware is configured.
> We're happy to contribute a patch since this causes some confusion when
> running with rack-aware replica placement.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
