[
https://issues.apache.org/jira/browse/KAFKA-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14143360#comment-14143360
]
Guozhang Wang commented on KAFKA-1590:
--------------------------------------
[~jkreps] agreed, binary log files should just be a option. What I proposed is
that instead of introducing a new config for that we can just set it indirectly
at the logging level. I.e. with trace level on the request logs, text log files
will be used; with debug level on request logs (which will only be logging
request summaries), the detailed log will also be written but as binary files.
[~abhi21]] Currently we use daily / hourly rolling, which I think is good
enough. Or do you have any ideas that needs size-based rolling?
> 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)
