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
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)
Hi Team,
I am trying to implement exactly once behavior in our source connector. Is
there any sample source connector implementation available to have a look
at?
Regards,
Nitty
When doing rolling restarts, I always wait until the under-replicated partition
count returns to zero before restarting the next broker. This state is achieved
AFTER the last restarted broker returns to a running state. If you just wait
for the running state, you risk restarting the next broker
Hello,
I'm doing some tests with rolling restarts in a Kafka cluster and I have a
couple of questions related to the impact of rolling restarts on Kafka
consumers/producers and on the overall process.
First, some context on my setup:
- Kafka cluster with 3 nodes.
- Topic replication
Dear Jakub,
Do you may know if anyone is able to test it, if we could set up a remote
Power10 unit ? Is this possible to be handled under any official process so
that an overall test // compilation // optimisation to all execs can be
enhanced for next version, so that compatibility matrix
Hello,
I'm doing some tests with rolling restarts in a Kafka cluster and I have a
couple of questions related to the impact of rolling restarts on Kafka
consumers/producers and on the overall process.
First, some context on my setup:
- Kafka cluster with 3 nodes.
- Topic replication
