We were initially having an issue with DBQ and heavy batch updates which used to result in many missing updates.
After reading many mails in mailing list which mentions that DBQ and batch update do not work well together, we switched to DBI. But we are seeing issue as mentioned in this jira issue: https://issues.apache.org/jira/browse/SOLR-7384 Specifically we are seeing a pattern as :- · There are several ERRORs and WARNs about “missing _*version*_” type of thing. · ERROR message is typically single. · There are several WARNs after that and after couple of WARNs there is message that Leader initiated recovery has been kicked off . Few scenarios: - Batch update with DBI where deletes are followed by updates for some documents in collection & Batch update with DBQ for some other docs => results in missing docs across both types - Batch deletes with DBI with route parameter, we see that about 20% of deletes are not happening. At this point there could be parallel batch updates with DBQ/ DBI - Pure DBI based updates where deletes are followed by updates , no DBQ here , but we are seeing missing version error and Leader initiated recovery, but deletes and updates seem fine for individual docs update, yet to test a batch with heavy load scenario *Setup info*: - Solr Cloud 6.6.2 --5 Node, 5 Shard, 3 replica setup -~35million docs in the collection - Nodes have 90GB RAM 32 to JVM -Soft commit interval 2 seconds, Hard commit (open searcher false) 15 seconds Are there any solutions to missing version update for DBI followed by LIR during heavy batch indexing wehn using custom routing ? Thanks, Sujatha
