[
https://issues.apache.org/jira/browse/SOLR-8709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226438#comment-15226438
]
Yonik Seeley commented on SOLR-8709:
------------------------------------
bq. It is possible that the way that flushes and commits are being processed
that out of order version numbers won't span commit boundaries.
How are commits being done? As you say, a reorder would need to cross a commit
boundary, and a search would need to be done at just that time for this to be
visible.
The number of commits are going to be far less than the number of document adds
(and reorders), even with something like a soft auto commit of 1 sec, so it's
not surprising that it's hard to see.
> Account for out-of-order version numbers in the TopicStream
> -----------------------------------------------------------
>
> Key: SOLR-8709
> URL: https://issues.apache.org/jira/browse/SOLR-8709
> Project: Solr
> Issue Type: Bug
> Reporter: Joel Bernstein
>
> Currently the TopicStream can miss documents if version numbers are received
> out-of-order. The TopicStream sorts on version number so it will only miss
> out-of-order versions that span commit boundaries.
> In order to resolve this issue we can adopt an approach that keeps a set of
> the last N version numbers sent for each Topic. As the documents are scanned
> we can check for documents within this time window that do not appear in the
> sent set. These documents can then be sent.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
