From 31dadf0242e2c4884035f9da1b67d2e916e33743 Mon Sep 17 00:00:00 2001 From: Manikumar Reddy Date: Thu, 7 May 2015 15:48:40 -0700 Subject: [PATCH] KAFKA-1884; Add logging upon metadata response errors; reviewed by Guozhang Wang --- .../src/main/java/org/apache/kafka/clients/NetworkClient.java | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/clients/src/main/java/org/apache/kafka/clients/NetworkClient.java b/clients/src/main/java/org/apache/kafka/clients/NetworkClient.java index b7ae595f2cc..435fbb5116e 100644 --- a/clients/src/main/java/org/apache/kafka/clients/NetworkClient.java +++ b/clients/src/main/java/org/apache/kafka/clients/NetworkClient.java @@ -391,6 +391,10 @@ public class NetworkClient implements KafkaClient { this.metadataFetchInProgress = false; MetadataResponse response = new MetadataResponse(body); Cluster cluster = response.cluster(); + // check if any topics metadata failed to get updated + if (response.errors().size() > 0) { + log.warn("Error while fetching metadata with correlation id {} : {}", header.correlationId(), response.errors()); + } // don't update the cluster if there are no valid nodes...the topic we want may still be in the process of being // created which means we will get errors and no nodes until it exists if (cluster.nodes().size() > 0) {