That is one awesome rebuttal, Jens. I read that forum topic below, and
while I have a great respect for Ezra (from his fine book Deploying
Rails Applications), I must say I disagree with him with respect to
Ferret/AAF combination.
We run Ferret/AAF as a DRb server in production and on our staging
servers and I've never seen a Ferret segfault. That said, we're not
high search load like Google, but even when hit with heavy load
testing, I haven't experienced a Ferret segfault, nor corrupt indexes.
Now, corrupt indexes in development is another issue. In development,
you are not running a DRb server. Each mongrel is hitting the index
directly. You typically have only one mongrel running in development.
But if you open an interactive script/console session, and play with
your models side-by-side a running mongrel, you WILL corrupt your
Ferret index. That's because both the mongrel and the script/console
will be writers to the same index, something that Ferret doesn't
support. Heck, running a rake db:migrate along side a running mongrel
will cause index corruption, for the same reason: multiple writers.
I'm wondering if that's why so many people experience Ferret indexing
problems in development? It's not immediately obvious that you're in a
multiple writer scenario some times.
For now, I'm sticking with the Ferret/AAF combination until one or the
other falls over completely.
Sheldon Maloff
Developer
http://ideas.veer.com
On 08-Aug-28, at 7:52 AM, Jens Kraemer wrote:
Hi!
On 27.08.2008, at 20:20, Eric Schulte wrote:
Thanks for all the info, I just found a very good related discussion
from ruby-forum which I thought I'd share
http://www.ruby-forum.com/topic/137629
well, in this discussion there's (besides some useful information)
some pretty biased statements from several people who obviously must
have had a frustrating time with Ferret, or just didn't get it
working right out of the box and decided it was cheaper to make
their clients switch search technology (and possibly losing
features) than to fix their deployment. I never had somebody from
engine yard contact me regarding their massive ferret deployment
problems, not sure how hard they really tried to get over them.
_______________________________________________
Ferret-talk mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/ferret-talk
