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 ------------------------------------------------ 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 3:40 PM, vsilgalis <vsilga...@gmail.com> wrote: > Michael Della Bitta-2 wrote >> With earlier versions of Solr Cloud, if there was any error or warning >> when you made a collection, you likely were set up for "implicit" >> routing which means that documents only go to the shard you're talking >> to. What you want is "compositeId" routing, which works how you think >> it should. >> >> Go into the cloud GUI and look at clusterstate.json in the Tree tab. >> You should see the routing algorithm it's using in that file. >> >> Michael Della Bitta > > That sounds like my huckleberry. > > "router":"implicit" > > Is in the collection info in the clusterstate.json > > How do I fix this? Just wipe the clusterstate.json? > > Thanks for your help. > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/SolrCloud-not-distributing-documents-across-shards-tp4053506p4053593.html > Sent from the Solr - User mailing list archive at Nabble.com.
