Hi Shawn

Absolutely perfect. It is always great reading your answers again and again as 
you explain the concepts so very well. Three cheers and thanks for your reply.

Regards,
Yavar
________________________________________
From: Shawn Heisey [s...@elyograg.org]
Sent: Wednesday, December 07, 2011 12:00 AM
To: solr-user@lucene.apache.org
Subject: Re: Autocommit & Index Size

On 12/6/2011 1:01 AM, Husain, Yavar wrote:
> In solrconfig.xml I was experimenting with Indexing Performance. When I set 
> the maxDocs (in autoCommit) to say 10000 documents the index size is double 
> to if I just dont use autoCommit (i.e. keep it commented, i.e commit at the 
> end only after adding documents).
>
> Does autoCommit affect the index size and if so why (as it should only affect 
> performance) ?

In other messages you have mentioned using MSSQL as a data source, so I
am taking a wild guess and assuming that you are running on Windows.  If
that's not the case, then I don't know why you are seeing this behavior.

On Windows, the timing involved when index segments are merged results
in the old index segments being left on the disk, because they are still
open for reading when Solr tries to delete them, and on Windows you
cannot delete an open file.  Later merge/optimize passes will remove
files left over from the previous passes, but will themselves suffer
from the same problem.

I am guessing that when you don't have autoCommit turned on, Solr never
opens an IndexReader on the segments as they are created, so Windows has
no trouble deleting old segments after merging/optimizing.  With
autoCommit turned on, Solr opens the index segments and makes them
searchable after every commit.

Thanks,
Shawn

******************************************************************************************
 
This message may contain confidential or proprietary information intended only 
for the use of the 
addressee(s) named above or may contain information that is legally privileged. 
If you are 
not the intended addressee, or the person responsible for delivering it to the 
intended addressee, 
you are hereby notified that reading, disseminating, distributing or copying 
this message is strictly 
prohibited. If you have received this message by mistake, please immediately 
notify us by 
replying to the message and delete the original message and any copies 
immediately thereafter. 

Thank you.- 
******************************************************************************************
FAFLD

Reply via email to