Also, another question, where it says to copy the zoo.cfg from /solr72/server/solr folder to /solr72/server/solr/node1/solr, should I actually be grabbing the zoo.cfg from one of my external zk nodes?
Thanks, Abhi On Thu, Mar 29, 2018 at 1:04 PM, Abhi Basu <9000r...@gmail.com> wrote: > Ok, will give it a try along with the host name. > > > On Thu, Mar 29, 2018 at 12:20 PM, Webster Homer <webster.ho...@sial.com> > wrote: > >> This Zookeeper ensemble doesn't look right. >> > >> > ./bin/solr start -cloud -s /usr/local/bin/solr-7.2.1/server/solr/node1/ >> -p >> > 8983 -z zk0-esohad,zk1-esohad,zk3-esohad:2181 -m 8g >> >> >> Shouldn't the zookeeper ensemble be specified as: >> zk0-esohad:2181,zk1-esohad:2181,zk3-esohad:2181 >> >> You should put the zookeeper port on each node in the comma separated >> list. >> I don't know if this is your problem, but I think your solr nodes will >> only >> be connecting to 1 zookeeper >> >> On Thu, Mar 29, 2018 at 10:56 AM, Walter Underwood <wun...@wunderwood.org >> > >> wrote: >> >> > I had that problem. Very annoying and we probably should require special >> > flag to use localhost. >> > >> > We need to start solr like this: >> > >> > ./solr start -c -h `hostname` >> > >> > If anybody ever forgets, we get a 127.0.0.1 node that shows down in >> > cluster status. No idea how to get rid of that. >> > >> > wunder >> > Walter Underwood >> > wun...@wunderwood.org >> > http://observer.wunderwood.org/ (my blog) >> > >> > > On Mar 29, 2018, at 7:46 AM, Shawn Heisey <apa...@elyograg.org> >> wrote: >> > > >> > > On 3/29/2018 8:25 AM, Abhi Basu wrote: >> > >> "Operation create caused >> > >> exception:":"org.apache.solr.common.SolrException:org. >> > apache.solr.common.SolrException: >> > >> Cannot create collection ems-collection. Value of maxShardsPerNode >> is 1, >> > >> and the number of nodes currently live or live and part of your >> > > >> > > I'm betting that all your nodes are registering themselves with the >> same >> > name, and that name is probably either 127.0.0.1 or 127.1.1.0 -- an >> address >> > on the loopback interface. >> > > >> > > Usually this problem (on an OS other than Windows, at least) is caused >> > by an incorrect /etc/hosts file that maps your hostname to a loopback >> > address instead of a real address. >> > > >> > > You can override the value that SolrCloud uses to register itself into >> > zookeeper so it doesn't depend on the OS configuration. In solr.in.sh, >> I >> > think this is the SOLR_HOST variable, which gets translated into >> -Dhost=XXX >> > on the java commandline. It can also be configured in solr.xml. >> > > >> > > Thanks, >> > > Shawn >> > > >> > >> > >> >> -- >> >> >> This message and any attachment are confidential and may be privileged or >> otherwise protected from disclosure. If you are not the intended >> recipient, >> you must not copy this message or attachment or disclose the contents to >> any other person. If you have received this transmission in error, please >> notify the sender immediately and delete the message and any attachment >> from your system. Merck KGaA, Darmstadt, Germany and any of its >> subsidiaries do not accept liability for any omissions or errors in this >> message which may arise as a result of E-Mail-transmission or for damages >> resulting from any unauthorized changes of the content of this message and >> any attachment thereto. Merck KGaA, Darmstadt, Germany and any of its >> subsidiaries do not guarantee that this message is free of viruses and >> does >> not accept liability for any damages caused by any virus transmitted >> therewith. >> >> Click http://www.emdgroup.com/disclaimer to access the German, French, >> Spanish and Portuguese versions of this disclaimer. >> > > > > -- > Abhi Basu > -- Abhi Basu
