[
https://issues.apache.org/jira/browse/SOLR-10112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15882638#comment-15882638
]
Ramsey Haddad commented on SOLR-10112:
--------------------------------------
We don't do many DBQs and we only use them to garbage collect stories that are
older than 10 days -- so, the type of race problems you are worried about are
not relevant to our specific use of DBQs.
But, still, I'm curious: do you see "Reordered DBQs detected" messages during
regular use?
We only see them as a side effect of the replaying operations during a
PeerSync. Do you see them outside of PeerSyncs?
> Prevent DBQs from getting reordered
> -----------------------------------
>
> Key: SOLR-10112
> URL: https://issues.apache.org/jira/browse/SOLR-10112
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Ishan Chattopadhyaya
>
> 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
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
