Thanks Erick for clarifying .. We are not explicitly setting the compositeId. We are using numShards=5 alone as part of the server start up. We are using uuid as unique field.
One sample id is : possting.mongo-v2.services.com-intl-staging-c2d2a376-5e4a-11e2-8963-0026b9414f30 Not sure how it would have gone to multiple shards. Do you have any suggestion for fixing this. Or we need to completely rebuild the index. When the routing key is compositeId, should we explicitly set "!" with shard key? -- View this message in context: http://lucene.472066.n3.nabble.com/Solr-Cloud-Duplicate-documents-in-multiple-shards-tp4218162p4218296.html Sent from the Solr - User mailing list archive at Nabble.com.
