We use the following merge policy on SSD's and are running on physical
machines with linux OS.
<mergeFactor>10</mergeFactor>
<mergePolicy class="org.apache.lucene.index.TieredMergePolicy"/>
<mergeScheduler
class="org.apache.lucene.index.ConcurrentMergeScheduler">
<int name="maxThreadCount">3</int>
<int name="maxMergeCount">15</int>
</mergeScheduler>
<ramBufferSizeMB>64</ramBufferSizeMB>
Not sure if its very aggressive, but its something we keep to prevent
deleted documents taking up too much space on our index.
Is there some error message that solr logs when rename and deletion of the
directories fails. If so we could monitor our logs to get a better idea for
the root cause. At present we can only react when things go wrong based on
disk space alarms.
Thanks,
Rishi.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Multiple-index-timestamp-directories-using-up-disk-space-tp4201098p4204145.html
Sent from the Solr - User mailing list archive at Nabble.com.
