Hi Franz,
The last bit of your command output shows that only one partition
(partition 3) is in sync, I've put asterisks around it, ISR being short
for In Sync Replicas
Hence why you're seeing that exception.
Topic: FooBar Partition: 0 Leader: 3 Replicas: 2,3,1 *Isr: 3*
I'd suggest looking in the logs for brokers 1 and 2 for any ReplicaFetcher
errors as a next step.
Cheers,
Liam Clarke-Hutchinson
On Sun, 27 Sep. 2020, 5:54 pm Franz van Betteraey, <fvbetteraey@web.de>
wrote:
> Hi all,
> <https://stackoverflow.com/posts/64080819/timeline>
>
> I have a strange Kafka Server error when mirroring data with the
> MirrorMaker 1 in Apache Kafka 2.6.
>
> |org.apache.kafka.common.errors.NotEnoughReplicasException: The size of
> the current ISR Set(3) is insufficient to satisfy the min.isr
> requirement of 2 for partition FooBar-0 |
>
> The strange thing is, that the |min.isr| setting is 2 and the ISR Set
> has 3 nodes. Nevertheless I get the /NotEnoughReplicasException/ Exception.
>
> Also taking a deeper look to the topic does not show any curiosities
>
> |[root@LoremIpsum kafka]# /usr/lib/kafka/kafka/bin/kafka-topics.sh
> --bootstrap-server localhost:9092 --describe --topic FooBar Topic:
> FooBar PartitionCount: 1 ReplicationFactor: 3 Configs:
>
> min.insync.replicas=2,cleanup.policy=compact,segment.bytes=1073741824,max.message.bytes=5242880,
> min.compaction.lag.ms
> =604800000,message.timestamp.type=LogAppendTime,unclean.leader.election.enable=false
> Topic: FooBar Partition: 0 Leader: 3 Replicas: 2,3,1 Isr: 3 |
>
> The logs of the 3 nodes look normal (as far as I can judge). Is there
> any other reason that could produce this message. What else could be
> checked?
>
> Thank you very much for any advice!
>
> I also posted this question on SO here:
>
> https://stackoverflow.com/questions/64080819/kafka-size-of-isr-set3-insufficient-for-min-isr-2
>
> Kind regards,
>
> Franz
>
>
The last bit of your command output shows that only one partition
(partition 3) is in sync, I've put asterisks around it, ISR being short
for In Sync Replicas
Hence why you're seeing that exception.
Topic: FooBar Partition: 0 Leader: 3 Replicas: 2,3,1 *Isr: 3*
I'd suggest looking in the logs for brokers 1 and 2 for any ReplicaFetcher
errors as a next step.
Cheers,
Liam Clarke-Hutchinson
On Sun, 27 Sep. 2020, 5:54 pm Franz van Betteraey, <fvbetteraey@web.de>
wrote:
> Hi all,
> <https://stackoverflow.com/posts/64080819/timeline>
>
> I have a strange Kafka Server error when mirroring data with the
> MirrorMaker 1 in Apache Kafka 2.6.
>
> |org.apache.kafka.common.errors.NotEnoughReplicasException: The size of
> the current ISR Set(3) is insufficient to satisfy the min.isr
> requirement of 2 for partition FooBar-0 |
>
> The strange thing is, that the |min.isr| setting is 2 and the ISR Set
> has 3 nodes. Nevertheless I get the /NotEnoughReplicasException/ Exception.
>
> Also taking a deeper look to the topic does not show any curiosities
>
> |[root@LoremIpsum kafka]# /usr/lib/kafka/kafka/bin/kafka-topics.sh
> --bootstrap-server localhost:9092 --describe --topic FooBar Topic:
> FooBar PartitionCount: 1 ReplicationFactor: 3 Configs:
>
> min.insync.replicas=2,cleanup.policy=compact,segment.bytes=1073741824,max.message.bytes=5242880,
> min.compaction.lag.ms
> =604800000,message.timestamp.type=LogAppendTime,unclean.leader.election.enable=false
> Topic: FooBar Partition: 0 Leader: 3 Replicas: 2,3,1 Isr: 3 |
>
> The logs of the 3 nodes look normal (as far as I can judge). Is there
> any other reason that could produce this message. What else could be
> checked?
>
> Thank you very much for any advice!
>
> I also posted this question on SO here:
>
> https://stackoverflow.com/questions/64080819/kafka-size-of-isr-set3-insufficient-for-min-isr-2
>
> Kind regards,
>
> Franz
>
>
Comments
Post a Comment