similar to: Ferret/AAF Stability?

I blogged about some of the problems with aaf in production (http://www.jroller.com/BrightCandle) yesterday but inspired by the poitive response I thought I would share the perceived problems and discuss some of the potential solutions to help newcomers and make aaf work as if by magic just like Rails does. All of these problems boil down to one simple problem, running acts as ferret in a

I''ve been running some multithreaded tests on Ferret. Using a single Ferret::Index::Index inside a DRb server, it definitely behaves for me as if all readers are locked out of the index when writing is going on in that index, not just optimization -- at least when segment merging happens, which is when the writes take the longest and you can therefore least afford to lock out all reads.

Hi. We use FerretDrb for search. If the ferret process is down, our entire application comes down the moment we try to save a model which is indexed. Is there a way to decouple this relationship such that we can somehow resume normal operations despite ferret being down and not index the model? Thanks. Morten

Hi folks! Does anyone have any example code for using a DRb Ferret server? No AAF. Dave - is yours ready? I know Jens has one, but I was hoping for something more stand-alone. I assume Jens has a lot of other code in there. Schnitz -------------- next part -------------- An HTML attachment was scrubbed... URL:

I''m sure I''m missing something completely obvious here, so I hope someone can point me in the right direction! I''ve implemented a basic search with AAF, which works as expected; I''m running a ferret drb server, and using will_paginate to page results. The code in my search_controller.rb: search_text = params[:query] || " " @products =

Hi, we still have the problem in that the Ferret Drb server dies on us sometimes. Looking through ferret_server.out and we come accross this: deadlock 0xb7261cb0: sleep:F(1012) - /usr/lib/ruby/1.8/drb/drb.rb:566 deadlock 0xb71d8654: sleep:F(409) - /usr/lib/ruby/1.8/drb/drb.rb:566 deadlock 0xb723f3e0: sleep:F(7) - /usr/lib/ruby/1.8/drb/drb.rb:566 deadlock 0xb72607c0: sleep:F(11) -

Jesse Grosjean wrote: > I''m trying to write a solaris SMF file to launch the ferret drb server. Hmm, I think I''ve hit a similar problem. I''ve just upgraded to the latest ferret trunk from an old aaf stable where the script/ferret_start and script/ferret_stop scripts were still in use. now if I call the old script... RAILS_ENV=production script/ferret_start

I am using AAF trunk, and I want a way to rebuild an index on a production site with little or no interruption to service. The Drb Server documentation* states that when an index is rebuilt, it is done in a separate location and then swapped into place when finished, and so to do a complete rebuild on a live site, one must take into consideration objects which have been created or

Hi all, I upgraded from Ferret 0.11.3 to Ferret 0.11.4 because I was getting intermittent segfaults that seemed to be due to a bug which was fixed (changeset 749). Unfortunately, 0.11.4 + acts_as_ferret seems to be a bad combination. I''m getting the some "fs_store/File Not Found Error occured at <except.c>:117" which was reported in the "Constant 0.11.4

Hi all, there was a recent thread[1] on rails-deploy about Ferret in which a lot of people complained of problems using it in production. I''ve been using Ferret (with DRb) for many months now with no serious issues. I''m assuming the posters know what they''re doing so I''m guessing they''re just using Ferret in higher-scale environments than me. I

Hi, I have my Model as follows: class Mutation < ActiveRecord::Base acts_as_ferret ({:fields => {:description=>{}, :product_id=>{:index => :untokenized}, :product_description=>{}, :product_label_description=>{}, :product_label_free=>{}, :product_product_id_supplier=>{}, :product_description_supplier=>{}, :supplier_description=>{}, :pub_date_sort

I am new to ferret and am just reading about it in the O''reilly shortcuts as well as other web resources. My app is a Rails app and so I am looking into acts_as_ferret as well. There are some questions for which I couldn''t find answers in the material I have read so far so I''d appreciate any help on these from the list. A bit of a background. My app will have 10,000 -

Hello all, I''m using AAF right now to index my ~3million db records. However, any additions to these records are added to the database through an external script so the aaf activerecord hooks will not catch any updates. Since new records are only added rarely, I figured I could just add the new records manually in ferret from some type of script. I''ve been looking at the

Hello, I am not able to run this command given in the tutorial http://projects.jkraemer.net/acts_as_ferret/ *Inside your Rails project* Please use script/plugin install svn://projects.jkraemer.net/acts_as_ferret/tags/stable/acts_as_ferret gem is installed. i have added the desired line in environment.rb as well but while running this particular command of svn://.. nothing actually

We''re running Ferret and acts_as_ferret in our production environment. We have multiple mongrels talking to a single index on a separate (virtual) server over DRb. This is working ok for now, as our index updates are fairly infrequent. I''m concerned with the lack of rendundancy/scalability in this layout. Our index won''t get too big - maybe 100k indexed objects, each no

I am implementing a search on my site and was wondering which will be the best way to go about it. We want a full text search and an advance search. We will have huge amounts of data that we would want to search. - on multiple tables. I went through the plugins acts_as_ferret and acts_as_solr. but ferret seems to have a locking problem at high load and solr needs a java server. So what do you

My project is currently using AAF 0.4.3. Trunk has some compelling features, but my project is going live on Monday and I am apprehensive about switching. Is anyone using trunk in a relatively high-volume context? (A low and vague standard for evaluating production suitability, I know, but better than nothing). Thanks, John

Is it possible to have one main ''index'', perhaps on a shared network drive, and have lots of instances of rails accessing it (though obviously with one db)? -- Posted via http://www.ruby-forum.com/.

Using the Drb allows me to synchronize writes to the index in a multi mongrel environment. I was under the impression that the remote index would not block if two mongrels were searching the index. Is that the case? This line in ferret_server.rb makes me think otherwise: # Calls are not queued atm, so this will block until the call returned. # def method_missing(name,

In my environment.rb I say the following: MyModel.disable_ferret puts MyModel.ferret_enabled? The console works as expected: script/console false >> MyModel.ferret_enabled? => false I can then edit an instance, ferret remains disabled and the changes are not immediately indexed. However, when I start mongrel Ferret is initially disabled, but then somehow becomes enabled again