>From what I can tell, the Collections API has been hardened significantly since 4.2 and now will refuse to create a collection if you give it something ambiguous to do. So if you upgrade to 4.2, things will become more safe.
But overall I'd find a way of using the Collections API that works and stick with it. Michael Della Bitta ------------------------------------------------ Appinions 18 East 41st Street, 2nd Floor New York, NY 10017-6271 www.appinions.com Where Influence Isn’t a Game On Wed, Apr 3, 2013 at 5:01 PM, vsilgalis <vsilga...@gmail.com> wrote: > Michael Della Bitta-2 wrote >> If you can work with a clean state, I'd turn off all your shards, >> clear out the Solr directories in Zookeeper, reset solr.xml for each >> of your shards, upgrade to the latest version of Solr, and turn >> everything back on again. Then upload config, recreate your >> collection, etc. >> >> I do it like this, but YMMV: >> >> curl >> "http://localhost:8080/solr/admin/collections?action=CREATE&name=$name&numShards=$num&collection.configName=$config-name"; >> >> >> Michael Della Bitta > > > Looks like that was the problem. Thanks, much appreciated. > > Is there any insight into specifically what I should look into for > preventing this in the future? > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/SolrCloud-not-distributing-documents-across-shards-tp4053506p4053622.html > Sent from the Solr - User mailing list archive at Nabble.com.
