I've a web application which uses Lucene for search functionality. Lucene
search requests are served by web services sitting on 2 application servers
(IIS 7).The 2 application servers are Load balanced using "netscaler".
Both these servers have a batch job running which updates search indexes on
09 12:10:42 AM
> Subject: Synchronizing Lucene indexes across 2 application servers
>
>
> I've a web application which uses Lucene for search functionality. Lucene
> search requests are served by web services sitting on 2 application servers
> (IIS 7).The 2 application serve
Or have a third master index, as Joel suggests, apply all updates to that
index, only, then at the end of each batch index update run, use rsync or
equivalent to push the master index out to the 2 search servers and then
tell them to reopen their indexes.
--
Ian.
On Fri, Jun 19, 2009 at 9:23 AM
do they have to be kept in synch in real time?
does each server handle writes to its own index which then need to be
propagated to the other server's index?
From a simplicity point of view, to minimise the amount of self consistency
checking that needs to happen I would suggest even having a thi
at any of
the 2 application servers could be serving search request depending upon its
availability.
Any inputs please?
Thanks for reading!
--
View this message in context:
http://www.nabble.com/Synchronizing-Lucene-indexes-across-2-application-servers-tp24105223p24105223.html
Sent from the Luce
