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

Posted to dev@kafka.apache.org by "Manikumar (JIRA)" <ji...@apache.org> on 2017/10/29 09:33:00 UTC

[jira] [Resolved] (KAFKA-536) Kafka async appender/producer looses most messages

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

Manikumar resolved KAFKA-536.
-----------------------------
    Resolution: Auto Closed

Closing inactive issue. 

> Kafka async appender/producer looses most messages
> --------------------------------------------------
>
>                 Key: KAFKA-536
>                 URL: https://issues.apache.org/jira/browse/KAFKA-536
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: nicu marasoiu
>
> The send thread reports Handling of 123 messages while the number of log lines was 11000 (the async appender is on rootLogger). Please advice.
> Another issue which we did solve was a log4j deadlock caused by the appender. We wrote our own appenders implementations that wrap the kafka implementation so that activateOption is delayed and executed outside log4j bootstrap, Please find more details on kafka-244 and its child



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)