You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Bart van Deenen (Jira)" <ji...@apache.org> on 2021/01/27 09:36:00 UTC

[jira] [Created] (KAFKA-12244) Deleting a topic within metadata.max.idle after last message floods log with warnings

Bart van Deenen created KAFKA-12244:
---------------------------------------

             Summary: Deleting a topic within metadata.max.idle after last message floods log with warnings
                 Key: KAFKA-12244
                 URL: https://issues.apache.org/jira/browse/KAFKA-12244
             Project: Kafka
          Issue Type: Improvement
          Components: producer 
    Affects Versions: 2.5.0
         Environment: Linux, Confluent 5.5.0
            Reporter: Bart van Deenen


In a test we produce to a topic, then stop producing and delete the topic ca. 30 seconds later.

This leads to a flood of WARN messages (ca. 10 per second) after several minutes that lasts for several minutes.

WARN org.apache.kafka.clients.NetworkClient - [Producer clientId=producer-2] Error while fetching metadata with correlation id 141 : \{test-topic=UNKNOWN_TOPIC_OR_PARTITION}

Investigation has shown that the issue can be solved by setting the metadata.max.idle.ms property to shorter than the interval between stopping messages and deleting the topic.

The issue itself is not critical, but can lead to a large pollution of your log, and thereby obscuring (or possibly losing) important messages.

 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)