similar to: aaf requires drb?

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

I''ve installed the ferret gem. I installed AAF as a plugin into my vendor/plugins directory of my project. In development environment my searches work just fine, without any problems. For production I configured the ferret_server.yml file with correct information about the machine my DRb server is running on. I start the ferret server with the following command: ruby script/runner

Hi all! We use the DRB-Server Backend and are getting strange DRb::DRbConnErrors lately. It started with: too large packet 687865856 (druby:/10.0.0.10:9010) /usr/lib/ruby/1.8/drb/drb.rb:573:in `load'' and later only this one: premature marshal format(can''t read) (druby:/10.0.0.10:9010) /usr/lib/ruby/1.8/drb/drb.rb:580:in `load'' Do you have any ideas what that

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''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 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

So my ferret behaves nicely in dev mode, but I just deployed and now he is not happy! First thing I noticed was that in general my app would not start with a folder called "development" in my index folder, so I changed it to "production" and now my app is functioning. However, when I try to search I get errors, which you can see here: http://pastie.caboo.se/61767 Im

Hi all, After switching from "regular" AAF to drb based my app is no longer handling nonlatin chars. Any hints? -- Posted via http://www.ruby-forum.com/.

Hi there, I''ve just started using aaf for searching and it''s running well apart from one error I received: A ThreadError occurred in person#search: current thread not owner (druby:/localhost:9010) /usr/lib/ruby/1.8/monitor.rb:274:in `mon_check_owner'' (druby:/localhost:9010) /usr/lib/ruby/1.8/monitor.rb:274:in `mon_check_owner''

(Sorry if some people see this twice. I originally posted this question from ruby-forum.com, but didn''t realize that the Ferret forum was a mirror and that I actually wasn''t a member.) Anyway, I''ve read all the documentation I could find, and read most of this forum, but I''m a still a little confused on running a ferret DRb server. All the examples seem to be

hello list! i''m still having massive problems with index rebuilds. after i recently switched to the DRb mode i was hoping to get rid of the problems with locked files and such. but even with DRb and the latest stable version of acts_as_ferret my index rebuilds are failing C:\Informer>ruby script/console production Loading production environment. >> LegacyInfobase.rebuild_index

Hi- I''m technical lead at Lingr (http://www.lingr.com), a chatroom-based social networking site. We''ve currently got several million user utterances stored in MySQL, and we''re looking to build a local search functionality. I''ve played around with aaf and I really like it, but I have some questions. 1. Is anyone out there using aaf to index a corpus of this

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

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

The problem with getting DRb to luanch on reboot is the same problem causing some people to ahve trouble getting mongrel clustersw to come back up on reboot. The problem is the PATH. ON many new RH distributions running SELinux, /usr/local/bin is not added to the PATH until reboot is complete. Therefore, those of having installed ruby in /usr/local/bin run in to issues. SO, hoping to save

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

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,

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},

After switching to the DRb server, I am experiencing strange behavior when sorting on score. My app was working as expected before the switch. Both before and after the switch, my app sorts properly on other fields, such as date. For sorting on score, I am using the following option find_by_contents option: :sort => Ferret::Search::SortField::SCORE Before switching to DRb, this worked

Hi folks! Just wanted to let you know that I released aaf 0.4.0 on last weekend. Besides the DRb server it also includes a new lazy loading feature that lets you do ferret searches without actually loading any records from the DB. Useful e.g. for live searches: model: class MyModel acts_as_ferret :fields => { :title => { :store => :yes }, :content => {} } end controller: