Thanks Mark. I meant ConcurrentMergeScheduler and ramBufferSizeMB (not maxBuffer). These are my settings for Merge.
/ <ramBufferSizeMB>960</ramBufferSizeMB> <mergeFactor>40</mergeFactor> <mergeScheduler class="org.apache.lucene.index.ConcurrentMergeScheduler"/> / --Shreejay Mark Miller-3 wrote > On Nov 9, 2012, at 1:20 PM, shreejay < > shreejayn@ > > wrote: > >> Instead of doing an optimize, I have now changed the Merge settings by >> keeping a maxBuffer = 960, a merge Factor = 40 and ConcurrentMergePolicy. > > Don't you mean ConcurrentMergeScheduler? > > Keep in mind that if you use the default TieredMergePolicy, mergeFactor > will have no affect. You need to use maxMergeAtOnce and segmentsPerTier > as sub args to the merge policy config (see the commented out example in > solrconfig.xml). > > Also, it's probably best to avoid using maxBufferedDocs at all. > > - Mark Mark Miller-3 wrote > On Nov 9, 2012, at 1:20 PM, shreejay < > shreejayn@ > > wrote: > >> Instead of doing an optimize, I have now changed the Merge settings by >> keeping a maxBuffer = 960, a merge Factor = 40 and ConcurrentMergePolicy. > > Don't you mean ConcurrentMergeScheduler? > > Keep in mind that if you use the default TieredMergePolicy, mergeFactor > will have no affect. You need to use maxMergeAtOnce and segmentsPerTier > as sub args to the merge policy config (see the commented out example in > solrconfig.xml). > > Also, it's probably best to avoid using maxBufferedDocs at all. > > - Mark -- View this message in context: http://lucene.472066.n3.nabble.com/Solr4-0-SolrCloud-queries-tp4016825p4020200.html Sent from the Solr - User mailing list archive at Nabble.com.