On Tuesday 13 December 2016 03:02 PM, Jaikiran Pai wrote:
log4j.logger.kafka.controller=*TRACE,* controllerAppender
log4j.additivity.kafka.controller=false
log4j.logger.state.change.logger=*TRACE*, stateChangeAppender
log4j.additivity.state.change.logger=false
Is it intentional to have this at TRACE level for the default shipped
config instead of having something like INFO or maybe DEBUG?
-Jaikiran
Having now looked at one of the log messages in that controller.log, I
don't think DEBUG level would be a good default either since it logs
messages which dump all topic names and the broker ids associated with
it very often at DEBUG level. Something like:
[2016-12-13 09:34:53,869] DEBUG [Controller 0]: preferred replicas by
broker Map.....
(note, I couldn't paste the exact log message, which was large, because
there wasn't a easy way to remove references to our application specific
names from it, for the topic names).
That single log message itself is huge every time since we have a large
number of topics which get created dynamically for our application use
case.
-Jaikiran
