Thanks Jack . Yes, this seems so !!
However I would like to fix this at code level by setting the noCFSRatio to
1.0 . But in solr 3.6.1 i am not able to find the build.xml file .
I suppose the build process has been changed since 1.3 ,can you throw some
light on how I can build source code post this change .
In 1.3 , I used to change the code from src file and compile and build
from the same directory as the build.xml file ,however all files seem to
be jarred now .Any pointers?
Regards
Sujatha
On Thu, Sep 20, 2012 at 5:36 AM, Jack Krupansky <j...@basetechnology.com>wrote:
> You may simply be encountering the situation where the merge size is
> greater than 10% of the index size, as per this comment in the code:
>
> /** If a merged segment will be more than this percentage
> * of the total size of the index, leave the segment as
> * non-compound file even if compound file is enabled.
> * Set to 1.0 to always use CFS regardless of merge
> * size. Default is 0.1. */
> public void setNoCFSRatio(double noCFSRatio) {
>
> Unfortunately there currently is no way for you to set the ratio higher in
> Solr.
>
> LogMergePolicy has the same issue.
>
> There should be some wiki doc for this, but I couldn't find any.
>
> -- Jack Krupansky
>
> -----Original Message----- From: Sujatha Arun
> Sent: Tuesday, September 18, 2012 10:00 PM
> To: solr-user@lucene.apache.org
> Subject: Re: Compond File Format Advice needed - On migration to 3.6.1
>
>
> anybody?
>
> On Tue, Sep 18, 2012 at 10:42 PM, Sujatha Arun <suja.a...@gmail.com>
> wrote:
>
> Hi ,
>>
>> The default Index file creation format in 3.6.1 [migrating from 1.3]
>> in-spite of setting the usecompoundfile to true seems to be to create non
>> compound files due to Lucene 2790<https://issues.apache.**
>> org/jira/browse/LUCENE-2790<https://issues.apache.org/jira/browse/LUCENE-2790>
>> >
>>
>> .
>>
>> I have tried the following ,but everything seems to create non compound
>> files ..
>>
>>
>> - set compound file format to true
>> - used the TieredMergePolicy, did not change maxMergeAtOnce and
>> segmentsPerTier.
>> - switched back to LogByteSizeMergePolicy but this also creates non
>>
>> compound files
>>
>> We are in a situation where we have several cores and hence several
>> indexes ,and do not want to run into too many open files error. What can
>> be
>> done to switch to compound file format from the beginning or will this
>> TiredMergepolicy lead us to too many open files eventually?
>>
>> Regards
>> Sujatha
>>
>>
>
