lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shay Banon (JIRA)" <>
Subject [jira] Commented: (LUCENE-2773) Don't create compound file for large segments by default
Date Wed, 24 Nov 2010 11:44:16 GMT


Shay Banon commented on LUCENE-2773:

Mike, are you sure regarding the default maxMergeMB set to 2gb? This ia a big change in default
behavior. For systems that do updates (deletes) we are covered because they are taken (partially)
into account when computing the segment size. But, lets say you have a 100gb size index, you
will end up with 50 segments, no?

> Don't create compound file for large segments by default
> --------------------------------------------------------
>                 Key: LUCENE-2773
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Index
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>             Fix For: 2.9.4, 3.0.3, 3.1, 4.0
>         Attachments: LUCENE-2773.patch
> Spinoff from LUCENE-2762.
> CFS is useful for keeping the open file count down.  But, it costs
> some added time during indexing to build, and also ties up temporary
> disk space, causing eg a large spike on the final merge of an
> optimize.
> Since MergePolicy dictates which segments should be CFS, we can
> change it to only build CFS for "smallish" merges.
> I think we should also set a maxMergeMB by default so that very large
> merges aren't done.

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