https://issues.apache.org/jira/browse/KAFKA-1647 sounds serious enough to
include in 0.8.2-beta if possible.
CONFIDENTIALITY NOTICE This message and any included attachments are from
Cerner Corporation and are intended only for the addressee. The information
contained in this message is
It doesn't look like a showstopper (all replicas for a partition going down
is rare and bigger issue if it happens) but it is good for folks to know
about it going in, definitely!
In either case I changed the fix version for that ticket to 0.8.2 so it
shows up now it is a blocker for final I
Another JIRA that will be nice to include as part of 0.8.2-beta is
https://issues.apache.org/jira/browse/KAFKA-1481 that fixes the mbean
naming. Looking for people's thoughts on 2 things here -
1. How do folks feel about doing a 0.8.2-beta release right now and 0.8.2
final 4-5 weeks later?
2. Do
+1 for a 0.8.2-beta next week and 0.8.2.0 final 4-5 weeks later.
I agree to the tickets you brought up to have in 0.8.2-beta and also
https://issues.apache.org/jira/browse/KAFKA-1493 for lz4 compression.
/***
Joe Stein
Founder, Principal Consultant
Big
Hi,
We have accumulated an impressive list of pretty major features in 0.8.2 -
Delete topic
Automated leader rebalancing
Controlled shutdown
Offset management
Parallel recovery
min.isr and
clean leader election
In the past, what has worked for major feature releases is a beta release
prior to a
