[jira] [Updated] (LUCENE-7301) updateNumericDocValue mixed with updateDocument can cause data loss in some randomized testing

["Hoss Man (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/LUCENE-7301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hoss Man updated LUCENE-7301:
-----------------------------
    Attachment: LUCENE-7301.patch

test demonstrating problem.

with the hardcoded {{setMaxBufferedDocs(3)}} this test fails on every seed i tried, but i suspect that number isn't magic and just has corollation with the number of updates in the test.

> updateNumericDocValue mixed with updateDocument can cause data loss in some randomized testing
> ----------------------------------------------------------------------------------------------
>
>                 Key: LUCENE-7301
>                 URL: https://issues.apache.org/jira/browse/LUCENE-7301
>             Project: Lucene - Core
>          Issue Type: Bug
>            Reporter: Hoss Man
>         Attachments: LUCENE-7301.patch
>
>
> SOLR-5944 has been held up by a while due to some extremely rare randomized test failures.
> Ishan and I have been working on whitling those Solr test failures down, trying to create more isolated reproducable test failures, and i *think* i've tracked it down to a bug in IndexWriter when the client calls to updateDocument intermixed with calls to updateNumericDocValue *AND* IndexWriterConfig.setMaxBufferedDocs is very low (i suspect "how low" depends on the number of quantity/types of updates -- but *just* got something that reproduced, and haven't tried reproducing with higher values of maxBufferedDocs and larger sequences of updateDocument / updateNumericDocValue calls.



--
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