Uploaded image for project: 'Lucene - Core'
  1. Lucene - Core
  2. LUCENE-2095

Document not guaranteed to be found after write and commit

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.4.1, 2.9.1
    • Fix Version/s: 2.9.2, 3.0.1, 4.0-ALPHA
    • Component/s: core/index
    • Labels:
      None
    • Environment:

      Linux 64bit

    • Lucene Fields:
      New

      Description

      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;

        Attachments

        1. LUCENE-2095.patch
          10 kB
          Michael McCandless
        2. lucene-stresstest.patch
          13 kB
          Sanne Grinovero

          Activity

            People

            • Assignee:
              mikemccand Michael McCandless
              Reporter:
              sanne Sanne Grinovero
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: