lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Lef (JIRA)" <>
Subject [jira] [Created] (LUCENE-4323) Add max cfs segment size to LogMergePolicy and TieredMergePolicy
Date Thu, 23 Aug 2012 11:13:42 GMT
Alexey Lef created LUCENE-4323:

             Summary: Add max cfs segment size to LogMergePolicy and TieredMergePolicy
                 Key: LUCENE-4323
             Project: Lucene - Core
          Issue Type: Improvement
          Components: core/index
    Affects Versions: 4.0-BETA
            Reporter: Alexey Lef
            Priority: Minor

Our application is managing thousands of indexes ranging from a few KB to a few GB in size.
To keep the number of files under control and at the same time avoid the overhead of compound
file format for large segments, we would like to keep only small segments as CFS. The meaning
of "small" here is in absolute byte size terms, not as a percentage of the overall index.
It is ok and in fact desirable to have the entire index as CFS as long as it is below the

The attached patch adds a new configuration option maxCFSSegmentSize which sets the absolute
limit on the compound file segment size, in addition to the existing noCFSRatio, i.e. the
lesser of the two will be used. The default is to allow any size (Long.MAX_VALUE) so that
the default behavior is exactly as it was before.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


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

View raw message