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

Large Lucene index can hit false OOM due to Sun JRE issue

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 2.4.1
    • Fix Version/s: 2.9
    • Component/s: core/index
    • Labels:
      None
    • Lucene Fields:
      New

      Description

      This is not a Lucene issue, but I want to open this so future google
      diggers can more easily find it.

      There's this nasty bug in Sun's JRE:

      http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6478546

      The gist seems to be, if you try to read a large (eg 200 MB) number of
      bytes during a single RandomAccessFile.read call, you can incorrectly
      hit OOM. Lucene does this, with norms, since we read in one byte per
      doc per field with norms, as a contiguous array of length maxDoc().

      The workaround was a custom patch to do large file reads as several
      smaller reads.

      Background here:

      http://www.nabble.com/problems-with-large-Lucene-index-td22347854.html

        Attachments

        1. LUCENE-1566.patch
          4 kB
          Simon Willnauer
        2. LUCENE-1566.patch
          4 kB
          Simon Willnauer
        3. LUCENE-1566.patch
          18 kB
          Michael McCandless
        4. LUCENE_1566_IndexInput.patch
          17 kB
          Simon Willnauer
        5. LUCENE_1566_IndexInput_Changes.patch
          14 kB
          Simon Willnauer
        6. LUCENE_1566_IndexInput_Changes.patch
          21 kB
          Simon Willnauer

          Activity

            People

            • Assignee:
              simonw Simon Willnauer
              Reporter:
              mikemccand Michael McCandless
            • Votes:
              3 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: