On Fri, 2008-01-04 at 12:37 -0800, Ezra Zygmuntowicz wrote: > Ferret is unstable in production. Segfaults, corrupted indexes > galore. We've switched around 40 clients form ferret to sphinx and > solved their problems this way. I will never use ferret again after > all the problems I have seen it cause peoples production apps. >
Just out of interest, were corrupted indexes seen even with only one process writing to the index (via DRb as is recommended)? Multiple writers are unsupported and cause these kinds of problems. Segfaults were quite common in older version too, but it's settled down now and I've had it rather stable in a few small production sites (though I'm not talking Twitter-like load :). John. -- http://www.brightbox.co.uk - UK Ruby on Rails hosting --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Deploying Rails" group. To post to this group, send email to rubyonrails-deployment@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-deployment?hl=en -~----------~----~----~----~------~----~------~--~---
