lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <>
Subject [jira] Resolved: (LUCENE-2097) In NRT mode, and CFS enabled, IndexWriter incorrectly ties up disk space
Date Thu, 10 Mar 2011 18:25:59 GMT


Michael McCandless resolved LUCENE-2097.

       Resolution: Fixed
    Fix Version/s: 3.1

This was separately fixed -- we now build the CFS before cutting over to it in the in-memory

> 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, 4.0
>         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.
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message