Andrey Falko created KAFKA-7894:
-----------------------------------
Summary: When Kafka detached from network; rack isn't logged
Key: KAFKA-7894
URL: https://issues.apache.org/jira/browse/KAFKA-7894
Project: Kafka
Issue Type: Bug
Reporter: Andrey Falko
Step 1: Broker is detached from network
Step 2: Logs show "rack: null" even through we have broker.rack set and correct
broker.rack shows up in the Kafka start sequence
java.io.IOException: Connection to ip-10-0-80-124.ec2.internal:9092 (id: 9
rack: null) failed.
22:58:02.354 WARN o.a.k.c.NetworkClient - [ReplicaFetcher replicaId=8,
leaderId=6, fetcherId=0] Error connecting to node
ip-10-0-11-22.ec2.internal:9092 (id: 6 rack: null)
22:58:02.354 INFO o.a.k.c.FetchSessionHandler - [ReplicaFetcher replicaId=8,
leaderId=6, fetcherId=0] Error sending fetch request (sessionId=685825590,
epoch=INITIAL) to node 6: java.io.IOException: C
onnection to ip-10-0-11-22.ec2.internal:9092 (id: 6 rack: null) failed..
java.io.IOException: Connection to ip-10-0-11-22.ec2.internal:9092 (id: 6 rack:
null) failed.
22:58:03.483 WARN o.a.k.c.NetworkClient - [ReplicaFetcher replicaId=8,
leaderId=5, fetcherId=0] Error connecting to node
ip-10-0-13-33.ec2.internal:9092 (id: 5 rack: null)
This seems similar to https://issues.apache.org/jira/browse/KAFKA-5463
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
