Guozhang,
We haven't enable message compression yet. In this case, what shall we do
when we upgrade to 0.8.2? Must we launch a new cluster, redirect the
traffic to the new cluster, and turn off the old one?
Thanks!
-Yu
On Tue, Dec 2, 2014 at 4:33 PM, Guozhang Wang wangg...@gmail.com wrote:
Thanks, Guozhang!
On Thu, Dec 4, 2014 at 9:08 AM, Guozhang Wang wangg...@gmail.com wrote:
You can still do the in-place upgrade, and the logs on the broker will be
then mixed with uncompressed and compressed messages. This is fine also
since the consumers are able to de-compress dynamically
Will doing one broker at
a time by brining the broker down, updating the code, and restarting it be
sufficient?
Yes this should work for the upgrade.
On Mon, Dec 1, 2014 at 10:23 PM, Yu Yang yuyan...@gmail.com wrote:
Hi,
We have a kafka cluster that runs Kafka 0.8.1 that we are considering
Yu,
Are you enabling message compression in 0.8.1 now? If you have already then
upgrading to 0.8.2 will not change its behavior.
Guozhang
On Tue, Dec 2, 2014 at 4:21 PM, Yu Yang yuyan...@gmail.com wrote:
Hi Neha,
Thanks for the reply! We know that Kafka 0.8.2 will be released soon. If
we
Hi,
We have a kafka cluster that runs Kafka 0.8.1 that we are considering
upgrade to 0.8.1.1. The Kafka documentation
http://kafka.apache.org/documentation.html#upgrade mentions upgrading
from 0.8 to 0.8.1, but not from 0.8.1 to 0.8.1.1. Will doing one broker at
a time by brining the broker
