Take everything I say with a grain of salt; I haven't set up a new Kafka
cluster from scratch in several years. And realistically, most users'
needs are better met with a simple deployment model with adequate
performance rather than a heavily tuned system. My attention was just
drawn to the bench
Hey Michael, thanks for your comments. I think the first of the
improvements you mentioned, the faster controller failover is a known
improvement to me. But the second one you suggest is a faster consumer
group failover, could you open that up a bit for me why do you think it
will be better on KRaf
The interesting numbers are the recovery times after 1) the Kafka broker
currently acting as the "active" controller (or the sole controller in a
ZooKeeper-based deployment) goes away; 2) the Kafka broker currently acting
as the consumer group coordinator for a consumer group with many partitions
a
Hi Paul,
I did some benchmarking as well and couldn't find a marginal difference
between KRaft and Zookeeper on end to end latency from producers to
consumers. I tested it on Kafka version 3.5.1 and used openmessaging's
benchmarking framework https://openmessaging.cloud/docs/benchmarks/ .
What I
Hi all,
We’ve previously done some benchmarking of Kafka ZooKeeper vs KRaft and found
no difference in throughput (which we believed is also what theory predicted,
as ZK/Kraft are only involved in Kafka meta-data operations, not data
workloads).
BUT – latest tests reveal improved producer and
