Hello everyone,
We’re experiencing an issue where Kafka clients are significantly delayed in
rediscovering the GroupCoordinator after the broker originally assigned as the
GroupCoordinator becomes unreachable.
In this scenario, while most clients are able to quickly locate a new
GroupCoordinat
Hi
Could you please give some clues about the pitfalls of this solution below?
We have 3 ZooKeepers in 3 data centers.
6 Kafka nodes in 2 data centers
replication factor=4
insync =3
unclean.leader.election.enable=false
We use rack.awareness to distribute partitions across data centers.
We
Hi,
If I understand correctly, the idempotent producer should be able to
guarantee that messages are not duplicated when the producer retries sends,
and as of https://issues.apache.org/jira/browse/KAFKA-5494, it should allow
for the producer to have multiple in flight requests at a time without
r
