lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simon Willnauer (JIRA)" <>
Subject [jira] Updated: (LUCENE-1566) Large Lucene index can hit false OOM due to Sun JRE issue
Date Mon, 29 Jun 2009 17:40:47 GMT


Simon Willnauer updated LUCENE-1566:

    Attachment: LUCENE-1566.patch

I was able to reproduce the bug on my machine using several JVMs. The attached patch is what
I got ready by now - I though I get it out there as soon as possible for discussion.
Test pass on my side!

> Large Lucene index can hit false OOM due to Sun JRE issue
> ---------------------------------------------------------
>                 Key: LUCENE-1566
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: Index
>    Affects Versions: 2.4.1
>            Reporter: Michael McCandless
>            Assignee: Simon Willnauer
>            Priority: Minor
>         Attachments: LUCENE-1566.patch
> 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:
> The gist seems to be, if you try to read a large (eg 200 MB) number of
> bytes during a single 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:

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