[
https://issues.apache.org/jira/browse/KAFKA-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15801283#comment-15801283
]
Edoardo Comar commented on KAFKA-1368:
--------------------------------------
Moving to Log4j v2 would allow dynamic reconfiguration of the logging levels
*without restarting the brokers* and without any API changes.
This could be done by a user, switching to the XML format, rather than
properties, and adding a directive like
{code:xml}
<Configuration monitorInterval="30">
{code}
as described here
http://logging.apache.org/log4j/2.x/manual/configuration.html#AutomaticReconfiguration
> 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
>
> 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.4#6332)
