similar to: Index location for multiple servers

I seem to be having problems with getting my searcher to be consistent while indexing. I am running the latest version of ferret (0.10.13) and I am using the Searchable plugin. Currently the way it indexes is by using a callback in the model of either after_update or after_create to index the fields that I have setup to be indexed. Right now I update the index about once every 4 or 5

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

I have a MySQL table with over 18 million records in it. We are indexing about 10 fields in this table with ferret. I am having problems with the initial building of the index. I created a rake task to run the "Model.rebuild_index" command in the background. That process ran fine for about 2.5 days before it just suddenly stopped. The log/ferret_index.log file says it got to about

Hi I use Ferret 0.11.4 and the latest stabel version of the acts_as_ferret plugin. To the issue. if I do Model.rebuild_index and after that try to update one of my objects of that Model I get: File Not Found Error occured at <except.c>:117 in xpop_context Error occured in fs_store.c:329 - fs_open_input tried to open

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 -

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! 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''m using acts_as_ferret in with a mongrel and I'' m getting locking errors that after a while result in a corrupt database. I know about the problem with different processes writing to the index but I haven''t been able to get the DRB server working properly yet. I read on this list that another solution is to set :auto_flush to true but I''m not

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

Hi, I use ferret 0.10.4 whith shared index over NFS directory. There are 2 applications servers. The web server is Mongrel 0.3.13.3 and mongrel_cluster 0.2.0. There are 20 Mongrel processes on each server. Each time my application update a model, Mongrel process stops running with this errro in its log: /usr/lib/ruby/gems/1.8/gems/ferret-0.10.4/lib/ferret/index.rb:663: [BUG] Segmentation fault

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

I have spent days trying to figure out how to get UTF-8 working with my site. Here''s my environment: Linux version 2.6.16.29-xen_3.0.3.0 Ruby 1.8.4 (2005-12-24 [i386-linux] Rails 1.2.3 mongrel (1.0.1) mongrel_cluster (1.0.2, 0.2.1) ferret (0.11.4) acts_as_ferret stable plugin Ferret DRB server When I don''t use an analyzer with my acts_as_ferret declaration, everything works

Greetings, I''ve been using ferret with great results now for a while, but in the last week, I''ve been running into some issues. I will occasionally see this message: Exception Message: Lock Error occured at <except.c>:103 in xpop_context Error occured in index.c:5368 - iw_open Couldn''t obtain write lock when opening IndexWriter Which is accompanied by

I''m trying to use the Ferret DRB server to avoid concurrency issues when using multiple mongrels. I can successfully add and edit data on my index via the DRB server, however, when I search the index, I get the following error: DRb::DRbConnError (DRb::DRbServerNotFound): /usr/lib/ruby/1.8/drb/drb.rb:1647:in `current_server'' /usr/lib/ruby/1.8/drb/drb.rb:1709:in

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

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 Everyone, I was wondering if folks here have had experience scaling Ferret beyond a single server? Currently, we are running Ferret in the same physical server as its Rails front end (via acts_as_ferret), but it is evident that we need a more scalable solution already. How would you split up the tasks (via dRB perhaps?) between two or three servers? Shared disk, replicated Ferret index (?),

Hi, I am looking for solution to work with ferret without DRB. I would like to turn off ferret indexing from application and use existing ferret index only for searching (read only), while I would create indexes once a day from script. Is it possible and how to turn indexing off and would ferret still complain if 2 mongrels try to open index file. thanks, Bojan -- Posted via

I''m having problems sorting on untokenized fields. I have one field that sorts fine, but there are others that seem to sort on a different field. Here''s the index description: acts_as_ferret :remote=>true,:fields=>{:name=>{:boost=>2},:name_for_sort=>{:index => :untokenized}, :city=>{:boost=>2}, :city_for_sort=>{:index=>:untokenized},