Roger found another possible issue with snappy compression that during
broker bouncing the snappy compressed messages could get corrupted while
re-sending. I am not sure if it is related but would be good to verify
after the upgrade.
Guozhang
On Tue, May 12, 2015 at 3:55 PM, Jun Rao
Hi Jun,
I figured it out this morning and opened
https://issues.apache.org/jira/browse/KAFKA-2189 --
it turned out to be a bug in versions 1.1.1.2 through 1.1.1.6 of
snappy-java that has recently
been fixed (I was very happy to see their new unit test named
Hi, Andrew,
Thanks for finding this out. I marked KAFKA-2189 as a blocker for 0.8.3.
Could you share your experience on snappy 1.1.1.7 in the jira once you have
tried it out? If the result looks good, we can upgrade the snappy version
in trunk.
Jun
On Tue, May 12, 2015 at 1:23 PM, Olson,Andrew
After a recent 0.8.2.1 upgrade we noticed a significant increase in used
filesystem space for our Kafka log data. We have another Kafka cluster still on
0.8.1.1 whose Kafka data is being copied over to the upgraded cluster, and it
is clear that the disk consumption is higher on 0.8.2.1 for the
