Hi Zhenyu,
> 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)
Controllers are always colocated with bro
For questions related to confluent, I think you'd better ask in their
channel.
Luke
On Fri, Mar 10, 2023 at 12:54 PM sunil chaudhari <
sunilmchaudhar...@gmail.com> wrote:
> Hi Luke,
> This docu is good.
> Does it apply for confluent as well?
>
>
>
> On Fri, 10 Mar 2023 at 8:47 AM, Luke Chen wro
Hi Luke,
This docu is good.
Does it apply for confluent as well?
On Fri, 10 Mar 2023 at 8:47 AM, Luke Chen wrote:
> Hi Zhenyu,
>
> Answering your question:
>
> > 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 K
Hi Zhenyu,
Answering your question:
> 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
That is not migrating, actually. That is just creating another kafka
cluster in KRaft mode.
The point for migra
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 st
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 wrote:
> Hi team,
>
> Here is a question about KRa
