We are using a recent Solr 3.x (See below for exact version). We have set the ramBufferSizeMB to 320 in both the indexDefaults and the mainIndex sections of our solrconfig.xml:
<ramBufferSizeMB>320</ramBufferSizeMB> <mergeFactor>20</mergeFactor> We expected that this would mean that the index would not write to disk until it reached somewhere approximately over 300MB in size. However, we see many small segments that look to be around 80MB in size. We have not yet issued a single commit so nothing else should force a write to disk. With a merge factor of 20 we also expected to see larger segments somewhere around 320 * 20 = 6GB in size, however we see several around 1GB. We understand that the sizes are approximate, but these seem nowhere near what we expected. Can anyone explain what is going on? BTW maxBufferedDocs is commented out, so this should not be affecting the buffer flushes <!--<maxBufferedDocs>1000</maxBufferedDocs>--> Solr Specification Version: 3.0.0.2010.11.19.16.00.54Solr Implementation Version: 3.1-SNAPSHOT 1036094 - root - 2010-11-19 16:00:54Lucene Specification Version: 3.1-SNAPSHOTLucene Implementation Version: 3.1-SNAPSHOT 1036094 - 2010-11-19 16:01:10 Tom Burton-West
