The default router has always been compositeId, but when you created your collection you may have created it with implicit. Looking at the clusterstate.json and/or state.json in the individual collection should show you (admin UI>>cloud>>tree).
But we need to be very clear about what a "duplicate" document is. Solr routes/replaces documents based on whatever you've defined as <uniqueKey> in your schema file (assuming compositeID routing). When you say you get dups when you re-index, it sounds like you are somehow using different <uniqueKey>s for what you consider the "same" document. bq: Also, 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. Hmmm. "update the config in all the solr machine...". You should not have to do this in SolrCloud. All the configs are stored in Zookeeper and loaded from ZK when the Solr instance starts. What it's starting to sound like is that you've somehow mixed up SorlCloud and older "stand-alone" concepts and "somehow" your restoration process messed up your configs. So if the issue isn't that you're somehow using different <unkiqueKey>'s, I'd recommend just starting over with a new collection since you can re-index from scratch. Best, Erick On Tue, Mar 14, 2017 at 10:35 AM, vbindal <vineetbin...@gmail.com> wrote: > Hi Shawn, > > We are on 4.10.0 version. Is that the default router in this version? Also, > we dont see all the documents duplicated, only some of them. I have a > indexer job to index data in SOLR. After I delete all the records and run > this job, the count is correct but when I run the job again, we start seeing > higher count and duplicate records (random records) in shards. > > Also, 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. > > > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Inconsistent-numFound-in-SC-when-querying-core-directly-tp4105009p4324937.html > Sent from the Solr - User mailing list archive at Nabble.com.
