Indeed, embedded Zookeeper is not stable even when I use it in my development servers. In production environment, always use different servers for Zookeeper and SolrCloud. Also, avoid using Windows system as best as you can. One reason is that zkServer.cmd tells the process that run Zookeeper by judging the DOS window title. However, according to what verison of Windows you use and how you start DOS window, it could be wrong. I have to modify the script to make it run ok under Windows (Note: I've posted some detail information/steps on this mail list before).
I've done same thing as Markus did. No matter single or multiple Solr instances, I always uses SolrCloud 5 although we have some old Solr 3.5 using HA proxy and master/slave configuration. But they all run under Linux. Scott Chu，scott....@udngroup.com 2016/7/29 (週五) ----- Original Message ----- From: Markus Jelsma To: solr-user CC: Date: 2016/7/28 (週四) 23:44 Subject: RE: Are there issues with the use of SolrCloud / embedded Zookeeperin non-HA deployments? Hello - all our production environments as deployed as a cloud, even when just a single Solr instance is used. We did this for the purpose having a single method of deployment / provisioning and just because we have the option to add replica's with ease if we need to. We never use embedded Zookeeper. Markus -----Original message----- > From:Andy C <andycs...@gmail.com> > Sent: Thursday 28th July 2016 17:38 > To: solr-user@lucene.apache.org > Subject: Are there issues with the use of SolrCloud / embedded Zookeeper in > non-HA deployments? > > We have integrated Solr 5.3.1 into our product. During installation > customers have the option of setting up a single Solr instance, or for high > availability deployments, multiple Solr instances in a master/slave > configuration. > > We are looking at migrating to SolrCloud for HA deployments, but are > wondering if it makes sense to also use SolrCloud in non-HA deployments? > > Our thought is that this would simplify things. We could use the same > approach for deploying our schema.xml and other configuration files on all > systems, we could always use the SolrJ CloudSolrClient class to communicate > with Solr, etc. > > Would it make sense to use the embedded Zookeeper instance in this > situation? I have seen warning that the embedded Zookeeper should not be > used in production deployments, but the reason generally given is that if > Solr goes down Zookeeper will also go down, which doesn't seem relevant > here. Are there other reasons not to use the embedded Zookeeper? > > More generally, are there downsides to using SolrCloud with a single > Zookeeper node and single Solr node? > > Would appreciate any feedback. > > Thanks, > Andy > ----- 未在此訊息中找到病毒。 已透過 AVG 檢查 - www.avg.com 版本: 2015.0.6201 / 病毒庫: 4627/12698 - 發佈日期: 07/28/16
