On Tue, Sep 12, 2006 at 10:57:32PM +0200, J Coppedge wrote: > I believe you touched on each one... > > 1. Shared network index. > > 2. Sync of centralized index to individual index on each "slave" server. > > 3. Centralizing the searching / indexing to a separate search server - > however it's possible that you would also need to load balance service > at some point...
load balancing the indexing to several servers can only be done via segmenting the data across those servers, and merging it when searching. This seems possible but is not implemented in Ferret (yet?) Java-Lucene has some kind of RMI stuff for searching multiple remote indexes afair. Even with 2 servers accessing the same physical index on a shared network drive you would see no indexing speed increase, since only one process may write-access the index at a time. searching speed would increase, of course. I don't know what amounts of traffic you expect, but I'd go with the simplest solution (besides the shared disk, where I'm somewhat unsure if it is possible) as long as possible: one centralized server handling all searching/indexing. fail safety could be reached with a replication of the index to another box, that steps in when needed. cheers, Jens > > > sounds really interesting... > > what other deployment scenarios did you think of ? > > > > -- > Posted via http://www.ruby-forum.com/. > _______________________________________________ > Ferret-talk mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/ferret-talk -- webit! Gesellschaft für neue Medien mbH www.webit.de Dipl.-Wirtschaftsingenieur Jens Krämer [EMAIL PROTECTED] Schnorrstraße 76 Tel +49 351 46766 0 D-01069 Dresden Fax +49 351 46766 66 _______________________________________________ Ferret-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/ferret-talk
