similar to: Mongrel Cluster Compatibility

I run a script that imports a few thousand records into the database. The script runs once for each of several XML files. What it does is parse the XML and for each element of a certain type creates a record in a rails database that gets indexed with acts_as_ferret. This worked fine before but today after a few files (70000 records) this started to happen for any file I tried:

Just a quick note for future reference - at least for me, ferret won''t work on Ruby 1.8.4. gem install ferret Successfully installed ferret-0.11.4-mswin32 ruby -v ruby 1.8.4 (2005-12-24) [i386-mswin32] irb irb(main):001:0> require ''ferret'' A windows error message box appears - ruby.exe - Entry Point Not Found The procedure entry point rb_w32_write could not be

I am having some great trouble keeping my Ferret indexer for ActiveRecord working. First the get_field_names disappears (now back), then I am collectig some major trouble with locking. Same thing here: exception 6 not handled: Could not obtain write lock when trying to write index A snippet like this just deadlocks retrying endlessly: begin @ferret_index << doc

I am getting this issue also... Does anyone know what this is? When will Acts as Ferret be available for v10? Thanks for your help in desperation! Caspar wrote: > Okay previous post related to me trying to fix this problem with an > upgrade to ferret 0.10.0 but acts as ferret is obviously not compatible > with this new version of ferret. > My app is about to go into production and

Cheers, I''ve just published a blog post about scaling Rails with Apache 2.2, mod_proxy_balancer and Mongrel. This way you do not need another proxy server or load balancer for Mongrel. Just use Apache 2.2 and mod_proxy balancer. http://blog.innerewut.de/articles/2006/04/21/scaling-rails-with-apache-2-2-mod_proxy_balancer-and-mongrel Jonathan -- Jonathan Weiss

Hi, I am experiencing very poor performance when updating my index. For example, to update the index for 10 documents, it is taking 3 to 4 seconds. My index is currently very small... with probably less than 100 docs in it. I have created my index as follows: GIFT_INDEX = Index::Index.new(:path => "#{index_dir}/gift", :key => ''id'', :auto_flush => true)

Hey gang, A post on the Rails forum a while back had it sound like you pretty much had to use the Index Readers & Writers if you were going to be potentially accessing an index from more than one process. (i.e. multiple dispatch.fcgi''s, etc) Is this still the case, or does the main Index class do that black magic behind the scenes? =) I was having trouble implementing the

I''d like to use Mongrel_cluster with SSL on a green-field application (it can be configured however is best - initially, "ease of setup" is important, but then soon after will be scaling and response time). I''ve read a lot of emails on this topic, and checked out the Mongrel pages, etc, but I''m left with this question of what is recommended: For a

I am indexing over 10,000 rows of data, it is very slow when it is indexing the 100,1000,10000 row, and now it is over 1 hour passed on the row 10,000. how to make it faster? here is my code: ================== doc = Document.new doc << Field.new("id", t.id, Field::Store::YES, Field::Index::UNTOKENIZED) doc << Field.new("title", t.title,

Hi - I upgraded to Ferret 0.11.3 from 0.10.13. I used to index 10,000 records in 10 secs. Now it takes 13 minutes. (That''s a factor of ~75x) Did something change in the flush semantics, or something? Thanks! Schnitz -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi all This week I have worked with Rails and Ferret to test Ferrets (and Lucenes) capabilities. I decided to make a mixin for ActiveRecord as it seemed the simplest possible solution and I ended up making this into a plugin. For more info on Ferret see: http://ferret.davebalmain.com/trac/ The plugin is functional but could easily be refined. Anyway I want to share it with you. Regard it as a

Hi all This week I have worked with Rails and Ferret to test Ferrets (and Lucenes) capabilities. I decided to make a mixin for ActiveRecord as it seemed the simplest possible solution and I ended up making this into a plugin. For more info on Ferret see: http://ferret.davebalmain.com/trac/ The plugin is functional but could easily be refined. Anyway I want to share it with you. Regard it as a

Hi folks, I''ve working and playing with acts_as_ferret and follow this fantastic tutorial: http://www.railsenvy.com/2007/2/19/acts-as-ferret-tutorial When I try to implement the field storage tip, it crash. So, I try to make it via script/console: 1. I have a simple model called Articles: class Article < ActiveRecord::Base acts_as_ferret :fields =>

> On 5/23/06, Walter <Walter at mwsewall.com> wrote: > [...] > > I realize that mongrel is not thread safe, I was hoping mongrel might > spawn a few processes and serve them in the background to emulate what I > wanted. > > > > Rails is not thread-safe. > Yes, that?s what I meant. <snip> > > The idea of the BackgroundDrb is that you perform

Hi Dave, I am using ferret at my site http://gifthat.com and I just had a few exceptions pop up. I don''t have a way to reproduce them, but my site just was listed on lifehacker.com and these issues have popped up under multiple concurrent users (only twice though which I think isn''t too bad). I am using two lighttpd instances both with read/write access to the index: 1) Error

Hi, I have been using Ferret on ruby-forum.com for a few days. While the searching works with reasonable performance, there are a lot of problems related to indexing. Sometimes the process hangs with 100% CPU usage, sometimes it leaves Lockfiles in the directory (causing other processes to fail while one ist still working), sometimes it even crashes with a segfault. I''m going to

I have a model class in rails that has a class variable that is a ferret index. For some reason, the methods in my class that refer to the class variable are getting lock conflicts. Can anybody see any obvious reason why? I notice that it keeps leaving a lock file in the index directory. I thought auto_flush was supposed to remove the lock automatically after every operation. Is there

Hi, I have ferret working fine on my Dev machine using a relative index path as follows: USER_INDEX = Index::Index.new(:path => "indexes/user", :key => ''id'', :auto_flush => true) And the indexes/user directory is located directly off the root of my project tree. But when I migrate this same code to my shared TextDrive account, Ferret cannot find the index

Our ferret 0.10.13 index has been slowly growing on our debian server and has just got up over 14,000 records. Yesterday I randomly noticed that one search I did was suddenly giving whack, unexpected results. I have spent much time trying to track the problem. Tried ferret 0.10.9 - no change. Tried on a windows machine - where it works fine, and doesn''t give weird results (which just

I''ve gotten several problems with C ferret crashing ruby. Here''s the stack trace of my latest case: #0 0x00000050 in ?? () #1 0xb74028ab in iw_close (iw=0x8685a40) at index_rw.c:947 #2 0xb7414359 in index_destroy (self=0x829ebc0) at ind.c:89 #3 0xb73f00bc in frt_ind_free (p=0x829ebc0) at r_search.c:1564 #4 0xb7f04dca in rb_gc_call_finalizer_at_exit () from