The first problem you had means that more than 60 connections (configured with the maxClientCnxns property in your zoo.cfg) were being attempted from the *same* IP - that’s a lot!
The second error seems rather truncated the way you’ve provided it - from Googling it seems there should be a bit more explanation or a longer stack trace. I wonder though if there’s been some kind of OS or network-level change that made ZK think all requests from all the clients were coming from the same IP, and that same change is now also preventing ZK from properly binding to whatever you’ve set up as the host:port for the server ids (which I assume you’ve removed and aren’t actually running with them blank as below). In other words, check that your config is still correct for the current network setup. On Jul 29, 2021, 5:50 AM -0500, Reej Nayagam <reej...@gmail.com>, wrote: > Hi All, > > Solr version - 8.8.2, Zookeeper - 3.6.3 > we have 3 zk's configured and there were no changes. > All of a sudden, we got a error, too many connection from 192.xx.xx. > maxconnection is 60. > > We stopped all the 3 zk's, cleared data and logs, and tried to restart, we > get the below error > > myid:1 warn NIOWorkerThread- NIOServerCnxn] close of session > java.io.IOException - Zookeeper server not running > at > org.apache.zookeeper.server.NIOServerCnxn.readlenght(nioservercnxn.java:544) > > zoo.cfg configs are as below > ticktime = 2000 > initLimit = 10 > synclimit = 5 > 4lw.commands.whitelist=mntr,conf,ruok > maxclientCnxnx=60 > admin.serverPort=8084 > dataDir=g:/solr_home/zookeeper/data > dataLogDir = g:/solr_home/zookeeper/logs > > server.1= > server.2= > server.3 = > > Kindly advice how to fix this and what might be the reason > > > > > *Thanks,* > *Reej*
