SOLR not deleting records
We have to SOLR colos. We issues a command to delete: IDS DELETED: 1000236662963, 1000224906023, 1000240171970, 1000241597424, 1000241604072, 1000241604073, 1000240171754, 1000241604056, 1000241604062, 1000237569503] COLO1 deleted everything but COLO2 skipped some of the records. For ex: 1000224906023 was not deleted. This happens consistently. We are running them in Hard-commit, Soft Commit is off. -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
Re: Inconsistent numFound in SC when querying core directly
Hi, I am facing the same issue where my query *:* returns inconsistent number (almost 3 ) time the actual number in millions. When I try disturb=false on every machine, the results are correct. but without `disturb=false` results are incorrect. Can you guys suggest something? -- View this message in context: http://lucene.472066.n3.nabble.com/Inconsistent-numFound-in-SC-when-querying-core-directly-tp4105009p4324561.html Sent from the Solr - User mailing list archive at Nabble.com.
Duplicate Documents which different version
I'm using solr 4.10.0. I'm using "id" field as the unique key - it is passed in with the document when ingesting the documents into solr. When querying on different shards, I get duplicate documents with different "_version_". Out off approx. milions of these docs are duplicates Cloud has 3 shards. 1 leader each shard (3 leaders in total). with approx 10 machines each shard. Thanks in advance for any insights. -- View this message in context: http://lucene.472066.n3.nabble.com/Duplicate-Documents-which-different-version-tp4324569.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Inconsistent numFound in SC when querying core directly
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.
Re: Inconsistent numFound in SC when querying core directly
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.
Re: Inconsistent numFound in SC when querying core directly
I think I dint explain properly. I have 3 data centers each with its own SOLR cloud. My original strategy was composite routing but when one data center went down and we brought it back, somehow the routing strategy on this changed to implicit (Other 2 DC still have composit and they are working absolutely fine). This might be the reason for the data corruption on that DS because the routing strategy got changed. If I changed the routing strategy back to composite (which it should be). is it ok? Do I need to do anything more than simply changing the strategy in the clusterState.json? -- View this message in context: http://lucene.472066.n3.nabble.com/Inconsistent-numFound-in-SC-when-querying-core-directly-tp4105009p4325001.html Sent from the Solr - User mailing list archive at Nabble.com.
