bq: However, the named core is created but not loaded in solr. I'm not quite sure what that means, what is the symptom you see? Because this should be fine. I've sometimes been fooled by looking at the core admin UI screen and not reloading it. What happens if you try querying your new collection directly right after you create it? e.g.
http://blah blah/solr/gagel/query?q=*:* You should get back a valid packet. Admittedly with 0 hits, but if the core were truly not loaded you'd get an error. And please, please, please do NOT use the core admin screen to try to add cores in SolrCloud mode. It's possible to use, but you must know _exactly_ what parameters to set or Bad Things Happen. Continue to use the collections API, it's safer. Best, Erick On Mon, Jul 6, 2015 at 8:54 AM, Jens Brandt <bra...@docoloc.de> wrote: > Hi, > > I am trying to setup SolrCloud with external zookeeper. Solr 5.2.1 is running > on host solrtest at port 8080 and zookeeper already contains a config with > the name customerSolr. When I create a new collection using the CollectionAPI > by calling the following url: > > http://solrtest:8080/solr/admin/collections?action=CREATE&numShards=1&collection.configName=customerSolr&name=gagel"; > > I get a positive response and the core name "gagel_shard1_replica1" is > returned. However, the named core is created but not loaded in solr. When I > trie to manually add the core by using the Core Admin webinterface I get the > error that the core already exists. After a restart of solr the core is > loaded correctly. > > Can anyone please advise if I am doing something wrong or maybe this is an > issue in solr 5.2.1? > > Best Regards, > Jens
