You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Rajini Sivaram (JIRA)" <ji...@apache.org> on 2018/01/02 12:31:00 UTC
[jira] [Created] (KAFKA-6415) KafkaLog4jAppender deadlocks when
logging from producer network thread
Rajini Sivaram created KAFKA-6415:
-------------------------------------
Summary: KafkaLog4jAppender deadlocks when logging from producer network thread
Key: KAFKA-6415
URL: https://issues.apache.org/jira/browse/KAFKA-6415
Project: Kafka
Issue Type: Bug
Components: log
Reporter: Rajini Sivaram
Fix For: 1.1.0
If a log entry in producer network thread in the metadata update path is appended to a Kafka topic using KafkaLog4jAppender, a new send is initiated from the network thread which cannot complete since the metadata wait triggered by the new send from the network thread waits for metadata from the network thread, resulting in a deadlock.
This was probably the case right from the beginning when KafkaLog4jAppender was introduced, but did not cause any issues so far since there were only debug log entries in that path which were not logged to a Kafka topic by any of the tests. A recent info level log entry introduced by the commit https://github.com/apache/kafka/commit/a3aea3cf4dbedb293f2d7859e0298bebc8e2185f is causing system test failures in log4j_appender_test.py due to the deadlock.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)