On Mon, Mar 26, 2007 at 05:20:47PM +0200, Andreas Korth wrote: > > On Mar 23, 2007, at 5:12 PM, Sebastien Pahl wrote: > > > Hi, > > > > I'm currently trying to set up a solution involving multiple servers > > using the same index over nfs. > > The problem is that from what I have seen, ferret doesn't support > > multiple processes writing to the same index. > > > > Using a DRb service is not an option since this would create a single > > point of failure. > > Did I miss something or is your NFS volume exactly that: a single > point of failure. I think you ruled out the DRb solution too quickly. > Shared resources on NFS volumes are always prone to failure. Plus it > doesn't scale well because too many processes accessing the index > directory will inevitably lead to poor performance or a complete > deadlock. > > I've come to the conclusion that the "Share Nothing" approach works > best and SOAs are the way to go. I prefer talking to a single index > server and not worry about the details. I don't care whether it is a > single server or a load balanced cluster that services my request.
Full ack :-) I don't know how big you expect your index to grow, and how critical it is that it's always up-to-date, but wouldn't it be sufficient to have a backup system with a nightly snapshot of the index, that could jump in in case the production server fails? You even could run continuous rebuilds on that backup server to keep the index fairly in sync... Jens -- Jens Krämer webit! Gesellschaft für neue Medien mbH Schnorrstraße 76 | 01069 Dresden Telefon +49 351 46766-0 | Telefax +49 351 46766-66 [EMAIL PROTECTED] | www.webit.de Amtsgericht Dresden | HRB 15422 GF Sven Haubold, Hagen Malessa _______________________________________________ Ferret-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/ferret-talk
