Why are you doing this in the first place? SolrCloud and master/slave are fundamentally different. When running in SolrCloud mode, there is no need whatsoever to configure replication as per the Wiki link you've outlined above, that's for the older style master/slave setups.
Just change it back and watch the magic would be my advice. So if you'd tell us why you thought this was necessary, perhaps we can suggest alternatives because from a quick glance it looks unnecessary, and in fact harmful. Best, Erick On Mon, Mar 23, 2015 at 10:08 PM, sthita <sthit...@gmail.com> wrote: > I have newly created a new collection and activated the replication for 4 > nodes(Including masters). > After doing the config changes as suggested on > http://wiki.apache.org/solr/SolrReplication > <http://wiki.apache.org/solr/SolrReplication> > The nodes of the newly created collections are down on solr cloud. We are > not able to add or remove any document on newly created core i.e dict_cn in > our case. All the configuration files look ok on solr cloud > > <http://lucene.472066.n3.nabble.com/file/n4194833/solr_issue.png> > > This is my replication changes on solrconfig.xml > > <requestHandler name="/replication" class="solr.ReplicationHandler" > startup="lazy"> > <lst name="master"> <str name="replicateAfter">commit</str> <str > name="replicateAfter">startup</str> > <str name="confFiles">solrconfig_cn.xml,schema_cn.xml</str> </lst> > > <lst name="slave"> <str name="masterUrl">http://mail:8983/solr/dict_cn</str> > </lst> > > Note: I am using solr 4.4.0, zookeeper-3.4.5 > > Can anyone help me on this ? > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Unable-to-setup-solr-cloud-with-multiple-collections-tp4194833.html > Sent from the Solr - User mailing list archive at Nabble.com.
