similar to: refreshing indexes?

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

Hi all, We''re attempting to use Ferret with the DRb server at the moment, and it doesn''t work, at all... = Executive Summary The DRb server process keeps on calling the remote index to the DRb server process... Which means DRb is calling itself, and itself, and itself, until Ruby kills the Thread with a SystemStackLevel error. = The excruciating details... # Mongrel is

I''m having problems getting the DRb server running with the aaf gem. I tried it with the plugin installed in my application, and it worked. I suspect the problem has something to do with the startup scripts expecting certain files to be in certain relative file paths. Any insights are appreciated, and maybe if you have time you can update the wiki document :) Thanks for a great

Hi, i''ve a project in wich i have 2 different rails apps accessing the same DB. The backoffice, as usual, changes data. The frontoffice has a search capabilities with acts_as_ferret (paginated) for search. Maybe this is a newbie question but, when i delete index and restart front app all the articles are indexed, but the new one''s (via backoffice) are not searchable. Does

Hello, I have been trying to set up the remote indexing for acts_as_ferret and followed the guide here: http://projects.jkraemer.net/acts_as_ferret/wiki/DrbServer I added :remote => true to my models and then specified host and port for the production environment. After defining the host/port for production, I tried to run my development server and received the following error:

Hi all, I cannot make aaf (rev. 220) use my custom analyzer, despite following the indications @ http://projects.jkraemer.net/acts_as_ferret/wiki/AdvancedUsage To pinpoint the problem, I created a model + a simple analyzer with 2 stop words : "fax" and "gsm". test 1 : model.rebuild_index + model.find_by_contents("fax") # fax is a stop word. => I get a

Hi folks, I have several models that index well in Drb mode. However, I have one scenario where it works in normal mode, but not in Drb mode. model A field :one end model B belongs_to :a field :two delegate :one, :to => :a acts_as_ferret :fields => { :one => {}, :two => {} }, :remote => true end If I leave off the :remote parameter, it works. Or, if I don''t

Hi! Aaf trunk has undergone several major refactorings the last days, with the result that you can now transparently switch your app from local to remote indexing and back :-) If you plan to scale your app to more than one physical machine, or if you have problems with corrupted indexes and the like under high load, you really should give this a try. I wrote some documentation to get you

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

Hi, I''d like to share the ferret indexes between deployments of a Rails app. At the moment the index is stored in #{RAILS_ROOT}/index meaning that it gets moved and must be rebuilt after every deploy. I guess the simplest solution would be to put it under log/ which is already shared by capistrano, any other ideas? Also, script/ferret_stop doesn''t work when run on a fresh

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

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. We''ve had some problems with ferret not being able to load our classes (stack trace below for the curious). I nailed it down to a deployment issue, where an old instance of ferret drb was running. I don''t understand the details quite yet, but the result was the the old ferret was never shutdown during redeployment, and attempts were made to start up a new one. Anywho,

Hi, I''m running the trunk version with drb server. In my ferret_server.log I get a lot of messages like this: #method_missing(:add, ["User", {:first_name=>"blah", :comments=>nil, :company=>"blah", :phone_day=>""}]) Over and over again. But more importantly, since yesterday doing a search has caused an exception: A NoMethodError

We''ve been running into problems with ferret indexing lately. The problem is intermittent and some times it persists. Just got this after wiping the index and redeploying: NoMethodError (undefined method `add'' for Solution:Class): (druby://10.1.65.87:9009) /data/releases/20071111152414/vendor/rails/activerecord/lib/active_record/base.rb:1238:in `method_missing''

Hi, I''ve just read some an article (http://www.jroller.com/BrightCandle/entry/oversights_in_rails_plugins_really.) This article (and the comment,) seem to imply that drb is required if running under a fastcgi kind of deployment. Is this true? Thanks, Chris. ps this is for a different server then my previous question. -- Posted via http://www.ruby-forum.com/.

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

Hello, First the specs: ruby 1.8.6, rails 1.2.3, ferret 0.11.4, mongrel 1.0.1, mongrel_cluster 0.2.1 And the model''s aaf config: # Ferret search engine acts_as_ferret({:fields => {:name => {:boost => 10}, :summary => {:boost => 2}, :body => {:boost => 1, :store => :no},

I am running ferret (0.11.4) and acts_as_ferret (stable from svn) in a rails 1.2.3 app in production using the DRb server. I recently upgraded my configuration and the method with which I start and stop the server no longer works: Here is the command I would like to use (and have used in the past) to start the aaf server: $ /Library/WebServer/rails/ccdb/current/script/runner -e production

I''m using DRb with edge [AAF] and my server is really fast reaching 3GB+ of memory and soon it will crash with this message: [FATAL] failed to allocate memory Now its like this: 10542 bbs 2 59 0 3649M 3647M sleep 1:27 0.10% runner Anybody has any ideas on this? -- Posted via http://www.ruby-forum.com/.