You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Chia-Ping Tsai (Jira)" <ji...@apache.org> on 2024/11/03 13:08:00 UTC

[jira] [Assigned] (KAFKA-13761) KafkaLog4jAppender deadlocks when idempotence is enabled

     [ https://issues.apache.org/jira/browse/KAFKA-13761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chia-Ping Tsai reassigned KAFKA-13761:
--------------------------------------

    Assignee: Yang Yu

> KafkaLog4jAppender deadlocks when idempotence is enabled
> --------------------------------------------------------
>
>                 Key: KAFKA-13761
>                 URL: https://issues.apache.org/jira/browse/KAFKA-13761
>             Project: Kafka
>          Issue Type: Bug
>          Components: log
>    Affects Versions: 3.1.0, 3.0.0, 3.0.1
>            Reporter: Yang Yu
>            Assignee: Yang Yu
>            Priority: Major
>
> KafkaLog4jAppender instantiates a KafkaProducer to append log entries to a Kafka topic. The producer.send operation may need to acquire locks during its execution. This can result in deadlocks when a log entry from the producer network thread is also at a log level that results in the entry being appended to a Kafka topic (KAFKA-6415).
> [https://github.com/apache/kafka/pull/11691] enables idempotence by default, and it introduced another place where the producer network thread can hit a deadlock. When calling TransactionManger#maybeAddPartition, the producer network thread will wait on the TransactionManager lock, and a deadlock can happen if TransactionManager also logs at INFO level. This is causing system test failures in log4j_appender_test.py
> Similar to KAFKA-6415, a workaround will be setting log level to WARN for TransactionManager in VerifiableLog4jAppender.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)