PS: Sorry if this is a repost, I was unable to see my message in the mailing
list - this may have been due to my outgoing email different from the one I
used to subscribe to the list with.
Overview – Trying to evaluate if keeping the index in memory using
RAMDirectoryFactory can help in query perf
I found a similar post -
http://lucene.472066.n3.nabble.com/Problems-with-RAMDirectory-in-Solr-td1575223.html
It mentions that Java based replication might work (This is what I have
used, but didn't work for me)
More interestingly it points out that OS's file system cache maybe able to
do this job
Thanks for the pointer to MMapDirectoryFactory.
Not having replication with RAMDirectoryFactory is a deal killer. We dont
want to index on the machines that serve queries.
>From what I can gather from reading, MMapDirectory + SSD could be a happy
medium.
I'll try to evaluate these a bit more form
hey
We have set locktype to simple in solrconfig.xml using:
simple. However on the page
localhost:8983/solr/admin/cores shows:
org.apache.lucene.store.MMapDirectory:org.apache.lucene.store.MMapDirectory/solr-cores/core0/data/index
lockFactory=*org.apache.lucene.store.NativeFSLockFactory*@3415d