On 7/11/2013 11:11 PM, Ranjith Venkatesan wrote: > tickTime in zookeeper was high. When i reduced it to 2000ms solr node status > gets updated in <20s. Hence resolved my issue. Thanks for helping me. > > I have one more question. > > 1. Is it advisable to reduce the tickTime further. > > 2. Or whats the most appropriate tickTime which gives maximum performance > and also solr node gets updated in lesser time. > > I hereby included my zoo.cfg configuration > > tickTime=2000 > dataDir=/home/local/ranjith-1785/sources/solrcloud/zookeeper-3.4.5_Server1/zoodata > clientPort = 2181 > initLimit=5 > syncLimit=2 > maxClientCnxns=180 > server.1=localhost:2888:3888 > server.2=localhost:3000:4000 > server.3=localhost:2500:3500
Here's mine, comments removed. Except for dataDir, these are all default values found in the zookeeper download and on the zookeeper website: tickTime=2000 initLimit=10 syncLimit=5 dataDir=zoodata clientPort=2181 server.1=zoo1.REDACTED.com:2888:3888 server.2=zoo2.REDACTED.com:2888:3888 server.3=zoo3.REDACTED.com:2888:3888 http://zookeeper.apache.org/doc/r3.4.5/zookeeperStarted.html#sc_RunningReplicatedZooKeeper I hope your config is a dev install, because if all your zookeepers are running on the same server, you have no redundancy in the face of a server failure. Servers do fail, even if they have all the redundancy features you can buy. Thanks, Shawn
