[
https://issues.apache.org/jira/browse/KAFKA-649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps updated KAFKA-649:
----------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
Closing as it looks like this was checked in.
> Cleanup log4j logging
> ---------------------
>
> Key: KAFKA-649
> URL: https://issues.apache.org/jira/browse/KAFKA-649
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 0.8.0
> Reporter: Jay Kreps
> Assignee: Jun Rao
> Priority: Blocker
> Attachments: KAFKA-649.v3.patch, KAFKA-649.v4.patch,
> KAFKA-649.v5.patch, KAFKA-649.v6.patch, kafka-649.patch, kafka-649_extra.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 was sent by Atlassian JIRA
(v6.2#6252)
