OK , but after re-election happened , consumers do not consume messages On Sun, Jan 20, 2019 at 4:18 PM suresh sargar <suresh.sar...@gmail.com> wrote:
> Zookeeper checks heartbeat of each node.as soon as ZK not able to get > heartbeat from leader, re-election happens. Heartbeat check interval is > configurable. If u run kafka_topic.sh with describe option u will see newly > elected leader and isr will also updated one. > > On Sun 20 Jan, 2019, 5:53 PM Amin Sadeghi <sadeghi.ya...@gmail.com wrote: > > > Thanks for answers > > But if a leader goes offline , when a follower become leader, in other > > words when a leader of partitions will changed > > > > On Sun, Jan 20, 2019 at 3:03 PM M. Manna <manme...@gmail.com> wrote: > > > > > I’m simply giving my comments but others please correct me if this is > not > > > correct. > > > > > > For Scenario 1 - your leader node0 is offline - and your quorum is now > > not > > > stable. So if a leader goes offline it's not certain who will take > over. > > So > > > that's why 3 is recommended as a minimum, however not the best number > to > > > deploy in production. > > > > > > For Scenario 2 - Your leader node0 is online. So even if node 1 or 2 is > > > stopped, the consumers can get the message from leaders, not followers. > > > > > > So this is not unexpected. > > > > > > Thanks, > > > > > > On Sun, 20 Jan 2019 at 11:17, Amin Sadeghi <sadeghi.ya...@gmail.com> > > > wrote: > > > > > > > Hi > > > > Please help me for kafka failover > > > > > > > > > > > > > > https://stackoverflow.com/questions/54274799/kafka-broker-failover-not-worked > > > > > > > > > >