[
https://issues.apache.org/jira/browse/KAFKA-3789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15395441#comment-15395441
]
Benoit Sigoure commented on KAFKA-3789:
---------------------------------------
Thanks, I'm not on kafka-dev so I hadn't seen this email. I ended up deploying
a snapshot build of trunk for the time being. For some reason I wasn't able to
rollback to v0.9.0.1, I was getting a weird {{NullPointerException}}, but now
that I have the snapshot version of v0.10.0.1 deployed, things are working fine
again.
> Upgrade Snappy to fix snappy decompression errors
> -------------------------------------------------
>
> Key: KAFKA-3789
> URL: https://issues.apache.org/jira/browse/KAFKA-3789
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 0.10.0.0
> Reporter: Grant Henke
> Assignee: Grant Henke
> Priority: Critical
> Fix For: 0.10.0.1
>
>
> snappy-java recently fixed a bug where parsing the MAGIC HEADER was being
> handled incorrectly: https://github.com/xerial/snappy-java/issues/142
> This issue caused "unknown broker exceptions" in the clients and prevented
> these messages from being appended to the log when messages were written
> using snappy c bindings in clients like librdkafka or ruby-kafka and read
> using snappy-java in the broker.
> The related librdkafka issue is here:
> https://github.com/edenhill/librdkafka/issues/645
> I am able to regularly reproduce the issue with librdkafka in 0.10 and after
> upgrading snappy-java to 1.1.2.6 the issue is resolved.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
