logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Sicker (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-1733) Add SyncSend attribute to KafkaAppender (as in KafkaLog4jAppender)
Date Mon, 23 Jan 2017 15:44:26 GMT

    [ https://issues.apache.org/jira/browse/LOG4J2-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15834777#comment-15834777

Matt Sicker commented on LOG4J2-1733:

Yeah, StatusLogger could be sufficient here depending on how serious those exceptions are.
I'll go make a new ticket for an async appender API.

> Add SyncSend attribute to KafkaAppender (as in KafkaLog4jAppender)
> ------------------------------------------------------------------
>                 Key: LOG4J2-1733
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1733
>             Project: Log4j 2
>          Issue Type: Improvement
>          Components: Appenders
>    Affects Versions: 2.5
>         Environment: Kafka
>            Reporter: Vincent Tieleman
>            Assignee: Mikael Ståldal
>             Fix For: 2.8
> The KafkaLog4jAppender (shipped with Kafka and usable with log4j), has a syncsend property
that improves performance significantly by not blocking a send to Kafka. I've tried many other
configuration settings and setups, but find that none of these approaches improved the logging
performance to Kafka as significantly as setting the syncsend property to false.
> Unfortunately, the syncsend property is not supported by the KafkaAppender shipped with
log4j2 and the KafkaLog4jAppender only supports log4j, so I am stuck with forking the code
and making the change myself.
> Could you please introduce this property in the KafkaAppender in log4j2?

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org

View raw message