kafka-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Liam Clarke-Hutchinson <liam.cla...@adscale.co.nz>
Subject Re: LeaderElectionNotNeededException
Date Fri, 16 Oct 2020 05:53:09 GMT
And to follow up on this, we rolled one of the 41% brokers, partition
leadership was redistributed to other brokers, but a preferred leader
election immediately led to the exact same distribution.

What's worse, is both of the 41% leadership brokers are in the same rack.

Very keen for advice, or in the worst case, recommendations on how to
manually elect leaders for a topic-partition to get us through the weekend.

Kind regards,


On Fri, 16 Oct. 2020, 6:22 pm Liam Clarke-Hutchinson, <
liam.clarke@adscale.co.nz> wrote:

> Kia ora,
> I am rather bemused by this one, I'll admit. Kafka version 2.4.0. We've
> been migrating topic-partitions from old broker machines to new brokers,
> have redistributed replicas evenly across the new brokers, removed the old
> brokers, and tried to run a preferred leader election.
> And when I did that, I got a "LeaderElectionNotNeededException", which I
> really disagree with, as two brokers out of six have 41% of partition
> leaders.
> I wonder if it's rack awareness messing with us or something? We are
> running two brokers in three AZs/racks with correctly configured rack.ids,
> but what are the origins of a "LeaderElectionNotNeededException"? And for
> the love of God, where is the parameter in the admin client for "I
> significantly disagree".
> Kind regards,
> Liam Clarke-Hutchinson

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message