On Wed, Oct 10, 2007 at 12:19:17PM -0700, Patrick Wright wrote: [..] > One alternate approach I'm considering would be to do something like this: > - disable the after_save callbacks in acts_as_ferret in production mode, to > stop multiple mongrels writing to the index. > - move all index writes to a centralized batch process which interacts with > a 'master' index > - periodically clone out the master index to slave indexes located locally > to each user-facing rails index (not using DRb)
should work. [..] > Does anyone have any experience with this kind of approach? Is there some > standard way to distribute and run multiple instances of an index? omdb.org uses rsync to sync index versions. > Bonus question - how upset does a running mongrel get when the ferret index > it talks to is suddenly replaced by a new set of files? Not upset at all if you do it like that: have two index directories and a symlink pointing to the one in use atm. Then sync to the currently unused index, change over the symlink and tell your mongrel to re-open it's searcher. Cheers, Jens -- Jens Krämer http://www.jkraemer.net/ - Blog http://www.omdb.org/ - The new free film database _______________________________________________ Ferret-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/ferret-talk
