You're still mixing master/slave with SolrCloud. Do _not_ reconfigure the replication. If you want your core (we call them replicas in SolrCloud) to appear on various nodes in your cluster, either create the collection with the nodes specified (createNodeSet) or, once the collection is created on any node (or set of nodes) do an ADDREPLICA (again with the collections API) where you want replicas to appear. The rest is automatic, i.e. the replica's index will be copied from the leader, all updates will be forwarded etc., without you doing any other configuration.
I think you're shooting yourself in the foot by trying to fiddle with replication. Or I misunderstand your problem entirely. Best, Erick On Tue, Mar 24, 2015 at 8:09 PM, sthita <sthit...@gmail.com> wrote: > Thanks Erick for your reply. > I am trying to create a new core i.e dict_cn , which is totally different in > terms of index data, configs etc from the existing core "abc". > The core is created successfully in my master (i.e mail) and i can do solr > query on this newly created core . > All the config files(Schema.xml and solrconfig.xml) are in mail server and > zookeper helps it for me to share all config files to other collections. > I did the similar setup to other collection , so that newly created core > should be available to all the collections, but it is still showing down. > > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Unable-to-setup-solr-cloud-with-multiple-collections-tp4194833p4195078.html > Sent from the Solr - User mailing list archive at Nabble.com.
