On Tue, Sep 12, 2006 at 07:33:19PM +0200, J Coppedge wrote: > Has anyone deployed ferret & act_as_ferret to a load balanced multiple > server environment? If so, did you simply use a shared network index?
I'm unsure if an index on a shared network drive would work. > I have a couple of ideas on how to deploy - but each have shortcomings > and I'm hoping to find out if anyone else has deployed ferret in this > manner. The application is simply load balanced between multiple > servers running the same app for speed and redundancy, and things that > are to be indexed could be changed at the same time on each instance - > and to make sure the index is up to date we'll be using acts_as_ferret, > but this seems to cause a potential problem when coming from multiple > servers to the same index. Any insight you could provide would > appreciated? interesting problem, that had to come up sooner or later :-) In case the 'index on a network drive' doesn't work out (file locking is one thing that could go wrong), I'd go for a central index server handling all the searching and indexing. This won't work with acts_as_ferret, though. If searching speed is an issue and accuracy of results is not, you could replicate the index to your app servers once in a while and search there. I feel it's time for acts_as_remote_ferret ;-) something like aaf, but connecting to a remote index server whenever a record is saved. Or implemented as an option to aaf, which then would be working on local indexes in development and test environments, and against a remote index server in production mode. sounds really interesting... what other deployment scenarios did you think of ? Jens -- 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
