[jira] [Commented] (SOLR-8647) Already open IndexSearcher sees different DVs as commits are happening

["Ishan Chattopadhyaya (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-8647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134165#comment-15134165 ] 

Ishan Chattopadhyaya commented on SOLR-8647:
--------------------------------------------

I can't seem to able to reproduce the problem that the DV value itself, when retrieved from the searcher after the commits in separate thread, is a different one than before. This is something, I think, is happening within the context of SOLR-5944. But now that I can't reproduce it in the context of these tests, I am not 100% sure is happening in SOLR-5944 too.

But the dvgen for the searcher's underlying segment reader is changing during a commit for sure.

> Already open IndexSearcher sees different DVs as commits are happening
> ----------------------------------------------------------------------
>
>                 Key: SOLR-8647
>                 URL: https://issues.apache.org/jira/browse/SOLR-8647
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Ishan Chattopadhyaya
>         Attachments: TestIndexSearcherStability.java, TestIndexSearcherStability.java
>
>
> While working on SOLR-5944, I ran into an issue whereby an already open IndexSearcher sees different views of the DVs as updates/commits are happening in different threads. This is resulting in inconsistency of DV values for the already open main searcher.
> When logging out the searcher, I can see that the searcher instance is same, but the dvgen and fieldinfogen values are changing for an existing searcher.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org