OK, so I have verified the two instances can run alongside, sharing the
same datadir
All update handlers are unaccessible in the read-only master
<updateHandler class="solr.DirectUpdateHandler2"
enable="${solr.can.write:true}">
java -Dsolr.can.write=false .....
And I can reload the index manually:
curl "
http://localhost:5005/solr/admin/cores?wt=json&action=RELOAD&core=collection1
"
But this is not an ideal solution; I'd like for the read-only server to
discover index changes on its own. Any pointers?
Thanks,
roman
On Tue, Jun 4, 2013 at 2:01 PM, Roman Chyla <roman.ch...@gmail.com> wrote:
> Hello,
>
> I need your expert advice. I am thinking about running two instances of
> solr that share the same datadirectory. The *reason* being: indexing
> instance is constantly building cache after every commit (we have a big
> cache) and this slows it down. But indexing doesn't need much RAM, only the
> search does (and server has lots of CPUs)
>
> So, it is like having two solr instances
>
> 1. solr-indexing-master
> 2. solr-read-only-master
>
> In the solrconfig.xml I can disable update components, It should be fine.
> However, I don't know how to 'trigger' index re-opening on (2) after the
> commit happens on (1).
>
> Ideally, the second instance could monitor the disk and re-open disk after
> new files appear there. Do I have to implement custom IndexReaderFactory?
> Or something else?
>
> Please note: I know about the replication, this usecase is IMHO slightly
> different - in fact, write-only-master (1) is also a replication master
>
> Googling turned out only this
> http://comments.gmane.org/gmane.comp.jakarta.lucene.solr.user/71912 - no
> pointers there.
>
> But If I am approaching the problem wrongly, please don't hesitate to
> 're-educate' me :)
>
> Thanks!
>
> roman
>
