Hello Jason, Thanks for Your quick response! The alternative of using the Solr replication is also still pending at this point, so we will consider its pros and cons, too.
Fortunately, we are not using AutoCommit in our project, as we need to control the creation of new segments, so I will propose to my colleagues that we issue a manual commit on the read-only node after successful index update. Just one more question: would it be possible in this case to use the same solrhome/conf directory (shared schema and solrconfig) and solr.xml file within both webapps? I guess we should then signal the read-only side each time the solr.xml has changed (additional cores may be added by the updating machine depending on the imported data). Thanks again and best regards! Milen -----Ursprüngliche Nachricht----- Von: Jason Hellman [mailto:jhell...@innoventsolutions.com] Gesendet: Freitag, 10. Mai 2013 17:30 An: solr-user@lucene.apache.org Betreff: Re: Sharing index data between two Solr instances Milen, At some point you'll need to call a commit to search your data, either via AutoCommit policy or deterministically. There are various schools of though on which way to go but something needs to do this. If you go the AutoCommit route be sure to pay attention to the openSearcher value. The default value of false will not cause an IndexSearcher to open the new data, and there is a strong use case for this.but if you're not aware you might be caught by surprise. Once the commit fires your search process will automatically see the new data, with no interruption to its queue of queries. You may also want to consider having a Master/Slave relationship via replication for higher availability. it is trivial to set up and works like a charm. Jason On May 10, 2013, at 8:14 AM, 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 >
