You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Matt Sicker (JIRA)" <ji...@apache.org> on 2017/02/25 07:44:44 UTC
[jira] [Commented] (LOG4J2-1824) (GC) Avoid allocating temporary
objects in KafkaAppender
[ https://issues.apache.org/jira/browse/LOG4J2-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15884136#comment-15884136 ]
Matt Sicker commented on LOG4J2-1824:
-------------------------------------
I also found this [alternative Kafka client library|https://github.com/blackberry/Krackle/] from the Kafka wiki if it turns out that decreasing temporary objects in the client itself is too difficult.
> (GC) Avoid allocating temporary objects in KafkaAppender
> --------------------------------------------------------
>
> Key: LOG4J2-1824
> URL: https://issues.apache.org/jira/browse/LOG4J2-1824
> Project: Log4j 2
> Issue Type: Improvement
> Components: Appenders
> Reporter: Matt Sicker
>
> Due to API limitations in kafka-clients, log messages must be encoded into byte arrays rather than directly into ByteBuffers via {{Encoder<LogEvent>}}-enhanced layouts. I've opened up KAFKA-4802 to get support on the client side for not converting the provided ByteBuffers back into a byte array, but in the meantime, KafkaAppender and KafkaManager can be enhanced to use the Encoder API.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org