Hi, I'm using Rails/AAF with Ferret 0.10.11, and my index occasionally 
(every few weeks, roughly) becomes corrupted.

If the index is busted, until I rebuild it our users are unable to save 
anything. I get errors like the one below, and the save rolls back.

My question is, is there any way to catch the error, and continue with 
the save even if the model isn't indexed? What would be ideal is if i 
could have a catch the error, and have it send me a notification, which 
would solve two problems: the save would still happen so our users 
wouldn't be impacted, and I would know exactly when the index had become 
corrupted, and could rebuild it.

TIA for any help,
John


here's the error i'm getting:


Processing UserController#signup (for 72.227.101.170 at 2006-10-31 
11:23:06) [POST]
  Session ID: 7f854fa9eaf95becbb9723a9bd48f9c2
  Parameters: {"user"=>{"subscribe_to_newsletter"=>"0", 
"password_confirmation"=>"[FILTERED]", "terms"=>"1", 
"password"=>"[FILTERED]", "login"=>"jmcgrath", 
"email"=>"[EMAIL PROTECTED]"}, "commit"=>"Sign Up", "action"=>"signup", 
"controller"=>"user"}
Unable to send confirmation E-Mail:
Lock Error occured at <except.c>:103 in xpop_context
Error occured in index.c:5371 - iw_open
        Couldn't obtain write lock when opening IndexWriter

-- 
Posted via http://www.ruby-forum.com/.
_______________________________________________
Ferret-talk mailing list
Ferret-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/ferret-talk

Reply via email to