kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ewen Cheslack-Postava (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-1368) Upgrade log4j
Date Sat, 03 Mar 2018 06:27:00 GMT

    [ https://issues.apache.org/jira/browse/KAFKA-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16384512#comment-16384512
] 

Ewen Cheslack-Postava commented on KAFKA-1368:
----------------------------------------------

Per original ticket, it looks like we've had log4j at 1.2.17 for almost 2 years already. Is
this ticket now really about upgrading to log4j 2.x, and should we update the title accordingly?

> 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
>            Priority: Major
>
> 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
(v7.6.3#76005)

Mime
View raw message