[
https://issues.apache.org/jira/browse/KAFKA-1352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13967159#comment-13967159
]
Joel Koshy commented on KAFKA-1352:
-----------------------------------
In this specific case given that there are a few fields I think it is
reasonable to have it on a single line but we should also have some coding
guideline on what is too much to have on a single line. E.g., see KAFKA-1122
i.e., I think there are cases where we probably should split (even if it means
a harder grep). I wonder if log4j or at least in its latest version has the
option of splitting large messages but putting the same timestamp on them.
> 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)
