You've specified bootstrap_confdir and the same collection.configName on all your cores, so as each of them start, each will be uploading its own configuration to the collection1_conf area of ZK, so they will all be overwriting each other.
Are your 4 cores replicas of the same collection or are they distinct collections? If the latter, then why put them all in SolrCloud (there really isn't any benefit?) but assuming you wanted to do it for expansion reasons (to add replicas later on), then each one will need to have a distinct collection.configName parameter, so that ZK knows to keep the configs separate. On 17 July 2013 07:44, smanad <sma...@gmail.com> wrote: > I am running solr 4.3 with tomcat 7 (with non SolrCloud) and have 4 solr > cores running. > > Switching to start using SolrCloud with tomcat7 and embedded zookeeper I > updated JAVA_OPTS in this file tomcat7/bin/setenv.sh to following, > > JAVA_OPTS="-Djava.awt.headless=true -Xms2048m -Xmx4096m > -XX:+UseConcMarkSweepGC -Dbootstrap_confdir=/<path>/solr/collection1/conf/ > -Dcollection.configName=collection1_conf -DnumShards=1 -DzkRun" > > Now, all my cores (collections) are set to the default collection1 schema. > Not sure why? > > solr.xml is set to correct instanceDir settings. > > Any pointers? > Thanks, > -Manasi > > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Switching-to-using-SolrCloud-with-tomcat7-and-embedded-zookeeper-tp4078524.html > Sent from the Solr - User mailing list archive at Nabble.com. >
