Hi Romi, after doing the changes, to se the impact you'll have to index some
documents, Solr won't change your index unless you add more documents and
commit them.
It looks like your maxMergeDocs parameter is too small, I would use a grater
value here.
You can see an good explanation on how the merge policy works in Solr here:
http://juanggrande.wordpress.com/2011/02/07/merge-policy-internals/
The default Merge policy has changed in 3_x and trunk, you can probably also
take a look at
http://blog.mikemccandless.com/2011/02/visualizing-lucenes-segment-merges.html
Regards,
Tomás
On Thu, Jun 30, 2011 at 6:47 AM, Romi romijain3...@gmail.com wrote:
my solrconfig.xml configuration is as :
mainIndex
useCompoundFilefalse/useCompoundFile
ramBufferSizeMB32/ramBufferSizeMB
mergeFactor5/mergeFactor
maxMergeDocs10/maxMergeDocs
maxFieldLength1/maxFieldLength
unlockOnStartupfalse/unlockOnStartup
/mainIndex
my solrconfig.xml configuration is as :
*mainIndex
useCompoundFilefalse/useCompoundFile
ramBufferSizeMB32/ramBufferSizeMB
mergeFactor5/mergeFactor
maxMergeDocs10/maxMergeDocs
maxFieldLength1/maxFieldLength
unlockOnStartupfalse/unlockOnStartup
/mainIndex*
and index size is 12mb. but when i change my mergeFactor i am not finding
any effect in my indexes., ie. the no of segments are exactly same. i am
not
getting which configuration will effect the no of segments. as i suppose it
is mergefactor. and my next problem is which configuration defines the
number of docs per segments and what will be the size of this segment so
that next segments will be created
please make me clear about these points
-
Thanks Regards
Romi
--
View this message in context:
http://lucene.472066.n3.nabble.com/MergerFacor-effect-on-indexes-tp3125146p3125146.html
Sent from the Solr - User mailing list archive at Nabble.com.
