[
https://issues.apache.org/jira/browse/ZOOKEEPER-3769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17068985#comment-17068985
]
Lasaro Camargos commented on ZOOKEEPER-3769:
--------------------------------------------
[~symat], thanks for the updated patch. I gave it a spin and it is working, as
in its not regressing anything else. I cannot confirm that it handles the issue
I had as I still haven't managed to reproduce.
Trying to answer your questions,
# There is nothing particular to this setup; all are physical boxes, running
on the same network, OS (centos 7) and java version (12)
# During the time the problem reproduced, I had multiple runs in which I just
restarted the service, but also runs in which I cleaned the setup. It
consistently reproduced, until it didn't. Whatever it was, it doesn't seem
related to the snapshots.
# Regarding dynamic reconfiguration, no, I haven't used it in this setup.
# You had asked me if I had tried Netty. Please ignore my previous response. I
didn't try it while the problem still reproduced.
Even if I cannot reproduce, I still think this is a fix worth having. Please
submit the PR.
Should I change the Jira name to better reflect what actually happened?
> fast leader election does not end if leader is taken down
> ---------------------------------------------------------
>
> Key: ZOOKEEPER-3769
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3769
> Project: ZooKeeper
> Issue Type: Bug
> Components: leaderElection
> Affects Versions: 3.5.7
> Reporter: Lasaro Camargos
> Assignee: Mate Szalay-Beko
> Priority: Major
> Attachments: node1.log, node2.log, node3.log
>
>
> 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
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
