similar to: Question on scalability

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 (?),

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

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

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

Hello. I''m the author of DataMapper (http://datamapper.org), and am trying to choose what Full-Text-Indexing engine/plugin I want to include by default. I was hoping you guys could help. :-) Sphinx comes highly recommended, but without live index updates, it just doesn''t seem practical for most of my work. I''m most experienced with Solr, but the whole HTTP::Request and

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

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

I''m wondering if someone can point me in a direction to monitor the ferret drb server while using cacti. Is it possible to run multiple instances of ferret drb on the same machine, just on different ports? Will it still update the index properly, or will you get collision? New to moving over to the drb server. Thanks. -- Posted via http://www.ruby-forum.com/.

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

Folks, Since upgrading to ferret 0.11.4 on Mac OS X Tiger, I''ve been running into constant crashes when running my Rails tests. Here''s an example of the output. -- snip -- 1) Error: test_published_blog_can_be_ferreted(BlogTest): Ferret::FileNotFoundError: File Not Found Error occured at <except.c>:117 in xpop_context Error occured in fs_store.c:329 - fs_open_input

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

Remember folks, we can support the Ferret project by donating warm soft electronic cash to the author, Dave Balmain, using the paypal buttons on the website: http://ferret.davebalmain.com/trac http://ferret.davebalmain.com/trac/wiki/DonationsFAQ We can also buy the Ferret Shortcut pdf/book from O''Reilly, also written by Dave Balmain. It''s awesome good:

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 ferreters: I''ve already posted this in rails, but someone there suggested this would be better. I''m getting a ferret error when I try to delete any item that has been previously indexed. I just installed ferret, so the indexes aren''t big or anything. What I''m trying to do is to just delete an item on a table that has been index. Here''s the error

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 -

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

I have seen several threads here and elsewhere about ferret and/or aaf causing seemingly random segfaults in mongrel. However, I didn''t see in any of these threads if a resolution was ever offered. I am currently experiencing this problem and I am keen to get a solution. I appreciate any update that anyone can give me. Best Regards, Danny -- Posted via http://www.ruby-forum.com/.

Hi, We''re happily using Ferret through acts_as_ferret on a Rails website, but we have an issue with rebuilding indexes. The Rails project directories are on an NFS mounted volume and running Model.rebuld_index there seems to take 60-100 times longer than it does on a local filesystem (e.g. /tmp). What we''d like to do is rebuild our indexes in say /tmp, then copy them back when

(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

I am having a strange problem starting the acts_as_ferret Drb server on a particular Linux machine (Debian Etch). The same setup works fine on my Mac (OSX). Without the Rails application running (yes, I''ve checked several times) I get the following error if I try to start the ferret server and one of my models contains :remote => true for acts_as_ferret: >> script/ferret_start