[
https://issues.apache.org/jira/browse/SOLR-10112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18132144#comment-18132144
]
Nick Shanin commented on SOLR-10112:
------------------------------------
>From code reading against apache/main b73f03976fa, the add path detects DBQs
>newer than an add and applies them with it through addAndDelete
>(solr/core/src/java/org/apache/solr/update/DirectUpdateHandler2.java:472-483,
>543-557). The open choice is whether the leader should hold updates behind a
>blocking barrier around every DBQ. Option one adds that barrier, which
>prevents reordering but costs write throughput while each DBQ waits for
>replicas. Option two closes the ticket, because reordered DBQs are already
>detected and handled. Which of these two options do you prefer?
🤖 AI-generated 🤖
> 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
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
