Regards number of partitions:
Still don't understand it fully.
I revisited Java default partitioner.
I see that there available partitions are used only when key is not provided
(virtually when it is round-robin).
When key is provided, it uses number of partitions (regardless of availability).
Thi
> On May 17, 2020, at 11:45 AM, Victoria Zuberman
> wrote:
>
> Regards acks=all:
> -
> Interesting point. Will check acks and min.insync.replicas values.
> If I understand the root cause that you are suggesting correctly, given my
> RF=2 and 3 brokers in cluster:
> m
Regards acks=all:
-
Interesting point. Will check acks and min.insync.replicas values.
If I understand the root cause that you are suggesting correctly, given my RF=2
and 3 brokers in cluster:
min.insync.replicas > 1 and acks=all, removing one broker ---> partition
th
If your producer is set to use acks=all, then it won’t be able to produce to
the topic topic partitions that had replicas on the missing broker until the
replacement broker has finished catching up to be included in the ISR.
What method are you using that reports on the number of topic partition
Hi,
Kafka cluster with 3 brokers, version 1.0.1.
Topic with 15 partitions, replication factor 2. All replicas in sync.
Bringing down one of the brokers (ungracefully), then adding a broker in
version 1.0.1
During this process, are we expected either of the following to happen:
1. Some of the
