Hello Peter, thanks for Your answer!
Indeed, we are considering replication as an alternative design. However, we are appealed by the idea of having the updated index almost instantly after successful import. Decision is still pending, though. Thanks and kind regards! Milen -----Ursprüngliche Nachricht----- Von: Peter Sturge [mailto:peter.stu...@gmail.com] Gesendet: Freitag, 10. Mai 2013 17:42 An: solr-user@lucene.apache.org Betreff: Re: Sharing index data between two Solr instances Hello Milen, We do something very similar to this, except we use separate processes on the same machine for the writer and reader. We do this so we can tune caches etc. to optimize for each, and still use the same index files. On MP machines, this works very well. If you've got 2 separate machines, I would have thought replication would be the way to go, as it performs the necessary syncronization for you. If you do share the same index files between 2 instances, you need to be aware of locking/contention issues (which it sounds like you are aware), and if they're on separate machines, you'll likely need some superfast shared disk channel (FC SAN or similar) to keep performance up (in our experience, Solr works best with fast local-attached storage - e.g. SSD or 15k SAS drives rather than SAN, and definitely not iSCSI or NAS). In order for the read-only instance to take the changes made by the writing instance, it will need to do an empty commit (i.e. no docs to commit - just auto-warming caches, readers etc.). For us, as our writer is constantly writing, we do a timed refresh on the read-only instance, but for separate machines you could use an rpc mechanism between the two instances. - again though, replication already does all this. Have you considered using replication? Thanks, Peter On Fri, May 10, 2013 at 4:14 PM, <milen.ti...@materna.de> wrote: > Hello together! > > I've been googleing on this topic but still couldn't find a definitive > answer to my question. > > We have a setup of two machines both running Solr 4.2 within Tomcat. > We are considering sharing the index data between both webapps. One of > the machines will be configured to update the index periodically, the > other one will be accessing it read-only. Using native locking on a > network-mounted NTFS, is it possible for the reader to detect when new > index data has been imported or do we need to signal it from the > updating webapp and make a commit in order to open a new reader with the > updated content? > > Thanks in advance! > > Milen Tilev > Master of Science > Softwareentwickler > Business Unit Information > ________________________________________________ > > MATERNA GmbH > Information & Communications > > Voßkuhle 37 > 44141 Dortmund > Deutschland > > Telefon: +49 231 5599-8257 > Fax: +49 231 5599-98257 > E-Mail: milen.ti...@materna.de<mailto:milen.ti...@materna.de> > > www.materna.de<http://www.materna.de/> | Newsletter< > http://www.materna.de/newsletter> | Twitter< > http://twitter.com/MATERNA_GmbH> | XING< > http://www.xing.com/companies/MATERNAGMBH> | Facebook< > http://www.facebook.com/maternagmbh> > ________________________________________________ > > Sitz der MATERNA GmbH: Voßkuhle 37, 44141 Dortmund > Geschäftsführer: Dr. Winfried Materna, Helmut an de Meulen, Ralph > Hartwig Amtsgericht Dortmund HRB 5839 > >
