Sorry, am a newbie myself, I was adding to the scenario where broker has
gone down and not come up when replication is 1, and a new leader is
elected, it will be the leader for this topic/partition, but if other
broker is down, it might not have the offsets?
On Sat, Aug 13, 2016 at 1:22 PM, Sudev
No why wouldn't the partition come back ?
Before preferred election there was leader serving the requests
during election when it tries to elect the preferred leader and the
preferred leader happens not to be in in ISR, fallback to leader leader
happens. After this producing/consuming from this par
But, isn't that assuming your topics are replicated to all brokers, in your
case there are no offsets probably for this reason too.
On Fri, Aug 12, 2016 at 2:23 PM, Zakee wrote:
> Typically "preferred leader election” would fail if/when one or more
> brokers still did not come back online after
Typically "preferred leader election” would fail if/when one or more brokers
still did not come back online after being down for some time. Is that your
scenario?
-Zakee
> On Aug 11, 2016, at 12:42 AM, Sudev A C wrote:
>
> Hi,
>
> With *auto.leader.rebalance.enable=true* Kafka runs preferre
Hi,
With *auto.leader.rebalance.enable=true* Kafka runs preferred election tool
in regular intervals rebalancing topic-partition leaders. Now if preferred
election fails to elect the preferred leader for a topic partition it falls
back to any other leader in ISR.
But for us in production when thi
