After careful reconsideration of the facts I eventually came to the conclusion that closing the index after write operations is good practice. I can recommend this approach to anyone running into the same problems.
My apologies for not RTFM. Cheers, Andy On 24.10.2006, at 02:51, Andreas Korth wrote: > Hi, > > I keep getting locking errors when updating my index which puzzles me > since only one process is supposed to be accessing the index at a > time (at least in development mode). > > I'm using Ferret with Rails (NOT acts_as_ferret, though) and employed > an observer to add a new document to the index when a new > ActiveRecord is created. I'm not sure if this has any impact on the > concurrency issues, but I thought I mention it. > > Find attached the verbatim error message and the relevant part of the > stack trace. > > Any ideas? > > Cheers, > Andreas _______________________________________________ Ferret-talk mailing list Ferret-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/ferret-talk
