[
https://issues.apache.org/jira/browse/KAFKA-1352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980538#comment-13980538
]
Jun Rao commented on KAFKA-1352:
--------------------------------
In terms of logging, it seems that
1. If we don't know from where the exception is going to be thrown, we can log
the stacktrace.
2. Otherwise, if we don't know the type of the exception, we can log e.toString
3. Otherwise, we can log e.getMessage
Agreed that the catching should be as specific as possible. In all cases when
we catch throwable, we just want to log our bugs (e.g., NullPointerException).
However, catching Exception may be enough. We can probably fix this is a
separate jira.
> Reduce logging on the server
> ----------------------------
>
> Key: KAFKA-1352
> URL: https://issues.apache.org/jira/browse/KAFKA-1352
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 0.8.0, 0.8.1
> Reporter: Neha Narkhede
> Assignee: Ivan Lyutov
> Labels: newbie, usability
> Fix For: 0.8.2
>
> Attachments: KAFKA-1352.patch, KAFKA-1352.patch,
> KAFKA-1352_2014-04-04_21:20:31.patch
>
>
> We have excessive logging in the server, making the logs unreadable and also
> affecting the performance of the server in practice. We need to clean the
> logs to address these issues.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
