[
https://issues.apache.org/jira/browse/KAFKA-3961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15375342#comment-15375342
]
Manikumar Reddy commented on KAFKA-3961:
----------------------------------------
you can try DumpLogSegments tools to to verify messages from data files. This
will give compression type for each message.
https://cwiki.apache.org/confluence/display/KAFKA/System+Tools#SystemTools-DumpLogSegment
> broker sends malformed response when switching from no compression to
> snappy/gzip
> ---------------------------------------------------------------------------------
>
> Key: KAFKA-3961
> URL: https://issues.apache.org/jira/browse/KAFKA-3961
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.10.0.0
> Environment: docker container java:openjdk-8-jre on arch linux
> 4.5.4-1-ARCH
> Reporter: Dieter Plaetinck
>
> Hi this is my first time using this tracker, so please bear with me (priority
> seems to be major by default?)
> I should be allowed to switch back and forth between none/gzip/snappy
> compression to the same topic/partition, right?
> (I couldn't find this explicitly anywhere but seems implied through the docs
> and also from https://issues.apache.org/jira/browse/KAFKA-1499)
> when I try this, first i use no compression, than kill my producer, restart
> it with snappy or gzip compression, send data to the same topic/partition
> again, it seems the broker is sending a malformed response to my consumer.
> At least that's what was suggested when i was reporting this problem in the
> tracker for the client library I use
> (https://github.com/Shopify/sarama/issues/698). Also noteworthy is that the
> broker doesn't log anything when this happens.
> thanks!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
