On Mon, Jan 22, 2007 at 12:25:13PM +0100, Manoel Lemos wrote: > Jens, > > Maybe you are correct. Actually my Rails application was UP. > I mean, while I was running Blog.rebuild_index on the console, the Rails > app was running. > > Is this the kind of simultaneous modification of the index that you > talked about?
exactly. > If yes, how will Ferret and Acts-As-Ferret behave in a real life > situation where we have several Mongrels running the Rails application? > Is this a problem? It should not, since Ferret is supposed to have a file system based locking that manages inter-process synchronisation. However it doesn't seem to be reliable under certain circumstances - the usual workaround is to use a backgroundrb process that does all the indexing, and only do the searching inside the mongrels. Unfortunately aaf does not support this kind of remote-indexing yet, but it is definitely on my list. > The Blog.rebuild_index is running, I'll let you know the results (now > with only the console running). Sounds like you index a whole Farm of Blogs - I'm still wondering about the reason for the long indexing time ;-) cheers, 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
