[ https://issues.apache.org/jira/browse/SOLR-10112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17056576#comment-17056576 ]
Eugene Tenkaev commented on SOLR-10112: --------------------------------------- [~ichattopadhyaya], [~rwhaddad] please help! We need to figure out root problem in our case. We are sending intensely updates that contains partial modification of fields in document using *set*. Also, we're sending delete by query(DBQ) pretty intensive, we use it for garbage collection of documents that don't have field *enabled* with value *true*. So if we want doc to be removed we set field *enabled:false*. Our delete by query(DBQ) looks like: {code} <delete><query>-enabled:true</query></delete> {code} Documents represent for example phone model. After some time it can be added back to search index and this doc will contain: {code} enabled:true {code} In parallel, we're enriching document by additional info, but we always make sure that update with *enabled:true* will be sent first before *other* updates. We start observer that we lose some *other* updates(updates that comes after first initial update with *enabled:true*). Seems like they not applied, can DBQs create such problems? Should we send DBQ's where we mention date and delete only documents that not have been updated for a day for example? Thank you, I will be very appreciated for help! > Prevent DBQs from getting reordered > ----------------------------------- > > Key: SOLR-10112 > URL: https://issues.apache.org/jira/browse/SOLR-10112 > Project: Solr > Issue Type: Bug > Reporter: Ishan Chattopadhyaya > Priority: Major > > Reordered DBQs are problematic for various reasons. We might be able to > prevent DBQs from getting re-ordered by making sure, at the leader, that all > updates before a DBQ have been written successfully on the replicas, and > block all updates after the DBQ until the DBQ is written successfully at the > replicas. -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org