Hi team, I have a zk cluster with three nodes with zk version 3.5.5.
zoo.cfg looks like this, with a exception that server.61 has an additional line extendedTypesEnabled=true: maxClientCnxns=300 reconfigEnabled=false 4lw.commands.whitelist=* snapCount=500000 initLimit=10 syncLimit=5 tickTime=2000 clientPort=2181 dataDir=/var/zookeeperdata server.61=10.xxx.130.61:2888:3888:participant server.222=10.xxx.130.222:2888:3888:participant server.21=10.xxx.131.21:2888:3888:participant After the cluster launched, ports 2888 and 3888 went to down accidently. For example, I've ever observe these scenarios: * 3888 went to down in server.222. I believe it has ever been up since at that time 222 was the leader and 61 was a follower but 21 failed to startup due to 3888 of 222 was down(21 started tens of minutes later than 222 and 61). How to find out what cause the down? I tried to search in zookeeper.out and zookeeper.log but doesn't recognize any suspicious. Does anyone has a keyword to search? * In another scenario where 61 is the leader while 21 and 222 is followers, 2888 is down in 21 and 222. But at the same time when I run zkCli.sh in node 222, I can change a key to a different value. Shouldn't a follower forward a write operation to leader through port 2888 then this would suppose to fail due to 2888 is down? BRs Fengtao Public
