The entire point of a Zookeeper cluster is that it continues to be available when one (or more) nodes are down.
If you want more failure tolerance, run a five node Zookeeper cluster instead of a three node cluster. Hacking the client will not increase robustness. Right now, you are hurting robustness by being too clever with the client. Hacking the client is not a last choice, it is a bad choice. For queries, there is not much benefit in running the cloud-aware client. A regular load balancer works just about as well. We use the Amazon load balancers. wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my blog) > On Jul 18, 2017, at 3:25 AM, wg85907 <gengwei...@sina.com> wrote: > > I am not mean my Zookeeper cluster is rebooting frequently, just want to > ensure my query service can be stable when Zookeeper cluster has issue or > reboot. Will do some test to check if there is some issue here. Maybe > current Zookeeper client can handle this case well. Hacking the client will > always be the last choice. > Regards, > Geng, Wei > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Create-too-many-zookeeper-connections-when-recreate-CloudSolrServer-instance-tp4346040p4346528.html > Sent from the Solr - User mailing list archive at Nabble.com.
