By default, the default merge policy (TieredMergePolicy) won't create the CFS if the segment is "very large" (> 10% of the total index size). Likely that's what you are seeing?
If you really must have a CFS (how come?) then you can call TieredMergePolicy.setNOCFSRatio(1.0) -- not sure how/where this is exposed in Solr though. LogMergePolicy also has the same behaviour/method... Mike McCandless http://blog.mikemccandless.com On Thu, May 3, 2012 at 5:18 AM, pravesh <suyalprav...@yahoo.com> wrote: > Hi, > > I've migrated the search servers to the latest stable release (SOLR-3.5) > from SOLR-1.4.1. > We've fully recreated the index for this. After index completes, when im > optimizing the index then it is not merging the index into a single .cfs > file as was being done with 1.4.1 version. > > We've set the , <useCompoundFile>true</useCompoundFile> > > Is it something related to the new MergePolicy being used with SOLR 3.x > onwards (I suppose it is TieredMergePolicy with 3.x version)? If yes should > i change it to the LogByteSizeMergePolicy? > > Does this change requires complete rebuilt OR will do incrementally? > > > Regards > Pravesh > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/SOLR-3-5-Index-Optimization-not-producing-single-cfs-file-tp3958619.html > Sent from the Solr - User mailing list archive at Nabble.com.
