[
https://issues.apache.org/jira/browse/LUCENE-2773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12935446#action_12935446
]
Michael McCandless commented on LUCENE-2773:
--------------------------------------------
OK i think for 2.9/3.0, I will only backport the "don't make a CFS if the
merged segment is large" change; that change will reduce temp disk space
required.
I think the change to maxMergeMB / take deletions into account is too big for
2.9/3.0.
So for 3.x/trunk (which already take deletions into account by default), I'll
switch maxMergeMB default to 2 GB. I think this is an OK default given that it
means your biggest segments will range from 2GB - 20GB.
> Don't create compound file for large segments by default
> --------------------------------------------------------
>
> Key: LUCENE-2773
> URL: https://issues.apache.org/jira/browse/LUCENE-2773
> 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: [email protected]
For additional commands, e-mail: [email protected]
