[ZOOKEEPER-3769] fast leader election does not end if leader is taken down

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.5.7
• Fix Version/s: 3.7.0, 3.6.1, 3.5.8
• Component/s: leaderElection
• Labels: pull-request-available
• Assignee: Mate Szalay-Beko
• Reporter: Lasaro Camargos
• Created: 24/Mar/20 18:49
• Updated: 11/May/20 15:41
• Resolved: 07/Apr/20 07:09

Description

In a cluster with three nodes, node3 is the leader and the other nodes are followers.

If I stop node3, the other two nodes do not finish the leader election.

This is happening with ZK 3.5.7,  openjdk version "12.0.2" 2019-07-16, and this config

 

tickTime=2000
initLimit=30
syncLimit=3
dataDir=/company/service/data
dataLogDir=/company/service/log
clientPort=2181
snapCount=100000
autopurge.snapRetainCount=3
autopurge.purgeInterval=1
skipACL=yes
preAllocSize=65536
maxClientCnxns=0
4lw.commands.whitelist=*
admin.enableServer=false

server.1=companydemo1.snc4.companyinc.com:3000:4000
server.2=companydemo2.snc4.companyinc.com:3000:4000
server.3=companydemo3.snc4.companyinc.com:3000:4000

 

Could you have a look at the logs and help me figure this out? It seems like node 1 is not getting notifications back from node2, but I don't see anything wrong with the network so I am wondering if bugs like  ZOOKEEPER-3756 could be causing it.

 

In the logs, node3 is killed at 11:17:14

node2 is killed at 11:17:50 2 and node 1 at 11:18:02 

 

 

 

Issue Links

• links to: GitHub Pull Request #1300
• links to: GitHub Pull Request #1305