You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Neha Narkhede (JIRA)" <ji...@apache.org> on 2014/09/12 05:34:33 UTC

[jira] [Updated] (KAFKA-1590) Binarize trace level request logging along with debug level text logging

     [ https://issues.apache.org/jira/browse/KAFKA-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Neha Narkhede updated KAFKA-1590:
---------------------------------
    Assignee: Abhishek Sharma

> Binarize trace level request logging along with debug level text logging
> ------------------------------------------------------------------------
>
>                 Key: KAFKA-1590
>                 URL: https://issues.apache.org/jira/browse/KAFKA-1590
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Guozhang Wang
>            Assignee: Abhishek Sharma
>              Labels: newbie
>             Fix For: 0.9.0
>
>
> With trace level logging, the request handling logs can grow very fast depending on the client behavior (e.g. consumer with 0 maxWait and hence keep sending fetch requests). Previously we have changed it to debug level which only provides a summary of the requests, omitting request details. However this does not work perfectly since summaries are not sufficient for trouble-shooting, and turning on trace level upon issues will be too late.
> The proposed solution here, is to default to debug level logging with trace level logging printed as binary format at the same time. The generated binary files can then be further compressed / rolled out. When needed, we will then decompress / parse the trace logs into texts.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)