Looking at the output you pasted, broker `0` was the one being upgraded? A
few things to check:
1. Does broker `0` connect to the other brokers after the restart
2. Is broker `0` able to connect to zookeeper
3. Does everything look OK in the controller and state-change logs in the
controller node
Yes, I've set the inter.broker.protocol.version=0.10.0 before restarting
each broker on a previous update. Clusters currently run with this config.
On 03/14/2017 12:34 PM, Ismael Juma wrote:
So, to double-check, you set inter.broker.protocol.version=0.10.0 before
bouncing each broker?
On
So, to double-check, you set inter.broker.protocol.version=0.10.0 before
bouncing each broker?
On Tue, Mar 14, 2017 at 11:22 AM, Thomas KIEFFER <
thomas.kief...@olamobile.com.invalid> wrote:
> Hello Ismael,
>
> Thank you for your feedback.
>
> Yes I've done this changes on a previous upgrade
Hello Ismael,
Thank you for your feedback.
Yes I've done this changes on a previous upgrade and set them
accordingly with the new version when trying to do the upgrade.
inter.broker.protocol.version=CURRENT_KAFKA_VERSION (e.g. 0.8.2, 0.9.0,
0.10.0 or 0.10.1).
Hi Thomas,
Did you follow the instructions:
https://kafka.apache.org/documentation/#upgrade
Ismael
On Mon, Mar 13, 2017 at 9:43 AM, Thomas KIEFFER <
thomas.kief...@olamobile.com.invalid> wrote:
> I'm trying to perform an upgrade of 2 kafka cluster of 5 instances, When
> I'm doing the switch
I'm trying to perform an upgrade of 2 kafka cluster of 5 instances, When
I'm doing the switch between 0.10.0.1 and 0.10.1.0 or 0.10.2.0, I saw
that ISR is lost when I upgrade one instance. I didn't find out yet
anything relevant about this problem, logs seems just fine.
eg.
kafka-topics.sh
