Hi Sunil, As mentioned earlier in my question, I have only one "combined" node as both controller and broker, and I totally accept downtime (stop service)
So just want to ask for my case, single node, if I want to upgrade to 3.4 then start service under KRaft (get rid of ZK), what would be the steps? Thanks~ On Mon, Mar 6, 2023 at 11:49 PM sunil chaudhari <sunilmchaudhar...@gmail.com> wrote: > How will you achieve zero downtime of you stop zookeeper and kafka? > There must be some standard steps so that stop zookeeper one by one and > start kraft same time so that it will be migrated gradually. > > > > On Tue, 7 Mar 2023 at 9:26 AM, Zhenyu Wang <stupidbea...@gmail.com> wrote: > > > Hi team, > > > > Here is a question about KRaft from normal user, who starts to use and > > learn Kafka since 3.2 > > > > Last month Kafka 3.4, the first bridge release was available, and I am > > considering to have a plan to use KRaft (get rid of ZK) since this > version > > > > Currently I am using 3.3.2 (upgrade from 3.2) with only one node, which > is > > both controller & broker, even ZK is installed on this node too (sorry I > > know it is not distributed and I will try to improve it with more > knowledge > > learned in future) > > > > When I read KIP-866, ZK to KRaft migration, from section Migration > > Overview, seems like the document is for multi-nodes with no or almost no > > downtime, enable KRaft node by node; however my case accepts downtime > (one > > node -_-!!), just want to have Kafka upgrade to 3.4 then start service > > under KRaft mode, make sure everything works well and no log lost > > > > Should I simply > > 1. download 3.4 binary > > 2. stop ZK & Kafka service > > 3. upgrade Kafka to 3.4 > > 4. start only Kafka service with KRaft server.properties > > > > Or any other thing I need to pay attention to? > > > > If there is a documentation as guide that would be quite helpful > > > > Really appreciate > > >
