similar to: Couple questions on BDRb and concurrent processing

Ahoy, I tried to install hieraki and it was a big mess. 1) upload_progress module needed to be installed 2) no test/development server configured in the config file so i had to add those 3) no log directory, had to add that 4) had to install 2 gems (ok fine) 5) once the server started, go to homepage and " NameError in Wiki/pageController#index uninitialized constant Node RAILS_ROOT:

Downloaded 290/290 and kernel panic, not syncing. Same old Linux. Fortunately, hadn't started updates, /home had been unmounted by some forward-looking individual and there was a sync;sync and blockdev -- flushbufs running every 15 seconds. =>:-o Pucker factor went from {O} to {o} to }{ the max! Anyway, a quick reboot, fsck, split the check-update into 2 arbitrary pieces and do it again.

I have two workers (ie two files in my RAILS_ROOT/lib/workers directory) on my Rails app. When I run a top on my box, I see *three* processes called packer_worker_r. Shouldn''t I just be having two? What is the third process for? Here is an extract of the output from my top command. The PIDs are 7084, 7085 and 7083. ============================================ PID USER PR NI VIRT

Hi, Just wondering how you setup and get bdrb running without rails? Many thanks

Hi, I''ve been having some issues integrating bdrb on a cruisecontrolrb server It''s related to the way we stop the bdrb server. The thing is, right now when we stop the process we are killing the parent of the group of the process. This is ok if you''re running script/backgroundrb stop directly from the console, but if I''m running this from another process,

I am sure..again I am missing something, but I am trying to start a worker, when backgroundrb starts and it doesn''t seem to work. Here is my config/backgroundrb_schedules.yml file: feed_worker: class: feed_worker job_key: feed_worker_key worker_method: do_work trigger_args: repeat_interval: 20.minutes I even tried this from Rails controller: # def start_feed_worker #

Hi, we are trying to use BDRB for background processing of long-running reports, and have two issues - one is that worker does not see our Report class from Rails, throws a: /var/apps/ror_trunk/vendor/plugins/backgroundrb/server/master_worker.rb:22:in `load'': undefined class/module Report (ArgumentError) from

Hi, Thanks for the help getting the new backgroundrb working, things are working fabulously now. I have two questions: 1) I have a few basic methods I need available on all my workers in order to communicate properly with my application... it seems to make the most sense right now to subclass BackgrounDRb::MetaWorker, or make a mixin module, because I''m actually extending some

Hi Folks, Well, Yesterday I pushed some more updates that I was cooking since last couple of days. Here is a brief list: 1. Results from worker stays even after a worker dies. 2. You can ask backgroundrb to store status objects in memcache cluster now. by default its stored in master process memory, but I have introduced an option to allow it to be stored in a memcache cluster:

I use BDRb to process RSS feeds for users on my site (http://feedflix.com). I have a batch job that queries the DB for records that haven''t been updated in the last so many hours and kicks off a background job for each of them. If N records are returned by the DB, N background jobs gets queued and get done serially. As long as N is 255 or under, everything works like a charm.

Hi, i''m going to implement a syndication-service, which will get lists in xml with some meta-data an enclosed video files, which will get encoded at the end. The syndication run will be startet every five minutes of a full hour. So i thought to build 4 Worker. One for checking which feeds to syndicate (syndication_worker) at a specific time, one for processing the list