You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Jeff Chao (JIRA)" <ji...@apache.org> on 2017/06/16 21:57:00 UTC
[jira] [Created] (KAFKA-5463) Controller incorrectly logs rack
information when new brokers are added
Jeff Chao created KAFKA-5463:
--------------------------------
Summary: 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.1, 0.10.2.0, 0.11.0.0
Environment: Ubuntu Trusty (14.04.5), Oracle JDK 8
Reporter: Jeff Chao
Priority: Minor
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)