lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <>
Subject [jira] Updated: (LUCENE-2095) Document not guaranteed to be found after write and commit
Date Sat, 28 Nov 2009 09:10:20 GMT


Michael McCandless updated LUCENE-2095:

    Attachment: LUCENE-2095.patch

Patch attached.  I think it's ready to commit:

  * Added a simple monitor lock during commit() to serialize threads.

  * Boiled down the test case to a new test case in TestIndexWriter.

  * Found & fixed the [unrelated] deadlock in TestCrash, and cutover
    RAMDir's tracking of sizeInBytes to an AtomicLong, as discussed on

> Document not guaranteed to be found after write and commit
> ----------------------------------------------------------
>                 Key: LUCENE-2095
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: Index
>    Affects Versions: 2.4.1, 2.9.1
>         Environment: Linux 64bit
>            Reporter: Sanne Grinovero
>            Assignee: Michael McCandless
>             Fix For: 2.9.2, 3.0.1, 3.1
>         Attachments: LUCENE-2095.patch, lucene-stresstest.patch
> after same email on developer list:
> "I developed a stress test to assert that a new document containing a
> specific term "X" is always found after a commit on the IndexWriter.
> This works most of the time, but it fails under load in rare occasions.
> I'm testing with 40 Threads, both with a SerialMergeScheduler and a
> ConcurrentMergeScheduler, all sharing a common IndexWriter.
> Attached testcase is using a RAMDirectory only, but I verified a
> FSDirectory behaves in the same way so I don't believe it's the
> Directory implementation or the MergeScheduler.
> This test is slow, so I don't consider it a functional or unit test.
> It might give false positives: it doesn't always fail, sorry I
> couldn't find out how to make it more likely to happen, besides
> scheduling it to run for a longer time."
> I tested this to affect versions 2.4.1 and 2.9.1;

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message