Hi, From my point of view, if you don't have any tool that help you in the management of your broker services, in other to do a rolling restart manually, you should shut down one broker at a time.
In this way, you leave time to the broker controller service to balance the active replicas into the healthy nodes. The same procedure when you start up your nodes. Regards! Alex Inviato da BlueMail<http://www.bluemail.me/r?b=13090> Il giorno 1 giu 2018, alle ore 07:31, Raghav <raghavas...@gmail.com<mailto:raghavas...@gmail.com>> ha scritto: Hi We have a 3 Kafka brokers setup on 0.10.2.1. We have a requirement in our company environment that we have to first stop our 3 Kafka Broker setup, then do some operations stuff that takes about 1 hours, and then bring up Kafka (version 1.1) brokers again. In order to achieve this, we issue: 1. Run *bin/<http://kafka-server-stop.sh>kafka-server-stop.sh<http://kafka-server-stop.sh>* at the same time on all three brokers. 2. Do operations on our environment for about 1 hour. 3. Run bin/kafka-server.-<http://start.sh>start.sh<http://start.sh> at the same time on all three brokers. Upon start, we observe that leadership for lot of partition is messed up. The leadership shows up as -1 for lot of partitions. And ISR has no servers. Because of this our Kafka cluster is unusable, and even restart of brokers doesn't help. 1. Could it be because we are not doing rolling stop ? 2. What's the best way to do rollling stop ? Please advise. Thanks. R ________________________________ -- The information transmitted is intended for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.
