lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <>
Subject [jira] Updated: (LUCENE-2097) In NRT mode, and CFS enabled, IndexWriter incorrectly ties up disk space
Date Sun, 29 Nov 2009 11:09:20 GMT


Michael McCandless updated LUCENE-2097:

    Attachment: LUCENE-2097.patch

Attached patch with test case that shows the issue.  Not yet sure what's the best way to fix
it... probably we have to build the CFS before opening the reader we want to pool.

> In NRT mode, and CFS enabled, IndexWriter incorrectly ties up disk space
> ------------------------------------------------------------------------
>                 Key: LUCENE-2097
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: Index
>    Affects Versions: 2.9, 2.9.1, 3.0
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>            Priority: Minor
>             Fix For: 3.1
>         Attachments: LUCENE-2097.patch
> Spinoff of java-user thread titled "searching while optimize"...
> If IndexWriter is in NRT mode (you've called getReader() at least
> once), and CFS is enabled, then internally the writer pools readers.
> However, after a merge completes, it opens the reader against het
> non-CFS segment files, and pools that.  It then builds the CFS file,
> as well, thus tying up the storage for that segment twice.
> Functionally the bug is harmless (it's only a disk space issue).
> Also, when the segment is merged, the disk space is released again
> (though the newly merged segment will also be double-tied-up).
> Simple workaround is to use non-CFS mode, or, don't use getReader.

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