That would make the problem even worse. If you created the collection with implicit routing, there are no hash ranges for each shard. CompositeId requires hash ranges to be defined for each shard. Don't even try.
Best, Erick On Tue, Mar 14, 2017 at 11:13 AM, vbindal <vineetbin...@gmail.com> wrote: > Compared it against the other 2 datacenters and they both have `compositeId > `. > > This started happening after 1 of our zookeeper died due to hardware issue > and we had to setup a new zookeeper machine. update the config in all the > solr machine and restart the cloud. My guess is something went wrong and > `implicit` router got created. > > Can I simply change the `clusterstate.json` to take care of this? > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Inconsistent-numFound-in-SC-when-querying-core-directly-tp4105009p4324950.html > Sent from the Solr - User mailing list archive at Nabble.com.
