Overview Trying to evaluate if keeping the index in memory using
RAMDirectoryFactory can help in query performance.I am trying to perform the
indexing on the master using solr.StandardDirectoryFactory and on the slave
using solr.RAMDirectoryFactory
Details:
We have set-up Solr in a master/slave enviornment. The index is built on the
master and then replicated to slaves which are used to serve the query.
The replication is done using the in-built Java replication in Solr.
On the master, in the <indexDefaults> of solrconfig.xml we have
<directoryFactory name="DirectoryFactory"
class="solr.StandardDirectoryFactory"/>
On the slave, I tried to use the following in the <indexDefaults>
<directoryFactory name="DirectoryFactory"
class="solr.RAMDirectoryFactory"/>
My slave shows no data for any queries. In solrconfig.xml it is mentioned
that replication doesn¹t work when using RAMDirectoryFactory, however this (
https://issues.apache.org/jira/browse/SOLR-1379) mentions that you can use
it to have the index on disk and then load into memory.
To test the sanity of my set-up, I changed solrconfig.xml in the slave to
and replicated:
<directoryFactory name="DirectoryFactory"
class="solr.StandardDirectoryFactory"/>
I was able to see the results.
Shouldn¹t RAMDirectoryFactory be used for reading index from disk into
memory?
Any help/pointers in the right direction would be appreciated.
Thanks!
