[ https://issues.apache.org/jira/browse/LUCENE-2773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12981726#action_12981726 ]
Michael McCandless commented on LUCENE-2773: -------------------------------------------- bq. Mike, this also means that an optimize will have no effect if all segments > 2GB with this as default? It seems kind of odd to me ey? There was a separate issue for this -- LUCENE-2701. I agree it's debatable... and it's not clear which way we should default it. > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org