lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simon Willnauer (JIRA)" <>
Subject [jira] Commented: (LUCENE-1566) Large Lucene index can hit false OOM due to Sun JRE issue
Date Thu, 16 Jul 2009 15:59:15 GMT


Simon Willnauer commented on LUCENE-1566:

bq. Simon can you take a look? 

I looked at it closely and did run testcases again. Looks good to me! Thanks for looking at
it again!


> 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
>             Fix For: 2.9
>         Attachments: LUCENE-1566.patch, LUCENE-1566.patch, LUCENE-1566.patch, LUCENE_1566_IndexInput.patch,
LUCENE_1566_IndexInput_Changes.patch, LUCENE_1566_IndexInput_Changes.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