kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Bagiev (JIRA)" <j...@apache.org>
Subject [jira] [Created] (KAFKA-8623) KafkaProducer possible deadlock when sending to different topics
Date Tue, 02 Jul 2019 10:51:00 GMT
Alexander Bagiev created KAFKA-8623:

             Summary: KafkaProducer possible deadlock when sending to different topics
                 Key: KAFKA-8623
                 URL: https://issues.apache.org/jira/browse/KAFKA-8623
             Project: Kafka
          Issue Type: Bug
          Components: producer 
    Affects Versions: 2.2.1
            Reporter: Alexander Bagiev

Project with bug reproduction: [https://github.com/abagiev/kafka-producer-bug]

It was found that sending two messages in two different topics in a row results in hanging
of KafkaProducer for 60s and the following exception:
org.springframework.kafka.core.KafkaProducerException: Failed to send; nested exception is
org.apache.kafka.common.errors.TimeoutException: Failed to update metadata after 60000 ms.
	at org.springframework.kafka.core.KafkaTemplate.lambda$buildCallback$0(KafkaTemplate.java:405)
	at org.apache.kafka.clients.producer.KafkaProducer.doSend(KafkaProducer.java:877) ~[kafka-clients-2.0.1.jar:na]
	at org.apache.kafka.clients.producer.KafkaProducer.send(KafkaProducer.java:803) ~[kafka-clients-2.0.1.jar:na]
	at org.springframework.kafka.core.DefaultKafkaProducerFactory$CloseSafeProducer.send(DefaultKafkaProducerFactory.java:444)
	at org.springframework.kafka.core.KafkaTemplate.doSend(KafkaTemplate.java:381) ~[spring-kafka-2.2.7.RELEASE.jar:2.2.7.RELEASE]
	at org.springframework.kafka.core.KafkaTemplate.send(KafkaTemplate.java:193) ~[spring-kafka-2.2.7.RELEASE.jar:2.2.7.RELEASE]
It looks like KafkaProducer requests two times for meta information for each topic and hangs
just before second request due to some deadlock. When 60s pass TimeoutException is thrown
and meta information is requested/received immediately (but after exception has been already

The issue in the example project is reproduced every time; and the use case is trivial.
 This is a critical bug for us.

This message was sent by Atlassian JIRA

View raw message