[
https://issues.apache.org/jira/browse/KAFKA-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15892265#comment-15892265
]
Ismael Juma commented on KAFKA-1368:
------------------------------------
[~ecomar], are you interested in picking this up? We could switch the broker's
`Logging` trait to use slf4j (like the clients) and then use the log4j 2.0
adapter: https://logging.apache.org/log4j/2.0/log4j-slf4j-impl/index.html.
Because of the compatibility implications, a KIP would be required. For users
who want to stick with log4j 1.x, they could replace the slf4j adapter.
> Upgrade log4j
> -------------
>
> Key: KAFKA-1368
> URL: https://issues.apache.org/jira/browse/KAFKA-1368
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 0.8.0
> Reporter: Vladislav Pernin
> Assignee: Mickael Maison
>
> Upgrade log4j to at least 1.2.16 ou 1.2.17.
> Usage of EnhancedPatternLayout will be possible.
> It allows to set delimiters around the full log, stacktrace included, making
> log messages collection easier with tools like Logstash.
> Example : <[%d{XXXX}]...[%t] %m%throwable>%n
> <[2014-04-08 11:07:20,360] ERROR [KafkaApi-1] Error when processing fetch
> request for partition [XXXXX,6] offset 700 from consumer with correlation id
> 0 (kafka.server.KafkaApis)
> kafka.common.OffsetOutOfRangeException: Request for offset 700 but we only
> have log segments in the range 16021 to 16021.
> at kafka.log.Log.read(Log.scala:429)
> ...
> at java.lang.Thread.run(Thread.java:744)>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
