[
https://issues.apache.org/jira/browse/KAFKA-649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guozhang Wang updated KAFKA-649:
--------------------------------
Status: Patch Available (was: Reopened)
Guidelines of cleaning:
1. Only errors causing the server to exit should be FATAL.
2. Otherwise, only errors that will cause message loss or corruption would be
ERROR, others would be WARN.
3. Only log the trace if it's not clear how the exception is hit.
4. Capitalize first letters.
> Cleanup log4j logging
> ---------------------
>
> Key: KAFKA-649
> URL: https://issues.apache.org/jira/browse/KAFKA-649
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 0.8
> Reporter: Jay Kreps
> Assignee: Jun Rao
> Priority: Blocker
> Attachments: kafka-649_extra.patch, kafka-649.patch,
> KAFKA-649.v3.patch
>
>
> Review the logs and do the following:
> 1. Fix confusing or duplicative messages
> 2. Assess that messages are at the right level (TRACE/DEBUG/INFO/WARN/ERROR)
> It would also be nice to add a log4j logger for the request logging (i.e. the
> access log) and another for the controller state change log, since these
> really have their own use cases.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
