[
https://issues.apache.org/jira/browse/KAFKA-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14151328#comment-14151328
]
Abhishek Sharma commented on KAFKA-1590:
----------------------------------------
[~jkreps] -
I am using Debian Linux and for Linux / Unix family, I surely suggest Midnight
Commander tool for reading and writing binary files.
IN case of MAC, I think any alternative tool of MC will work. HexEdit is
another option that I googled out, haven't worked on it but I am sure it
supports.
In Case of Windows, I think Total Commander will work.
[~guozhang] & [~nehanarkhede] - I am sure, you people have some other tool /
utility programs names to suggest. Please suggest.
> 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
>
> Attachments: Jira-1590-Log4j Binary Appender.patch
>
>
> 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)
