[Backgroundrb-devel] best practices for robust workers
leeslist at gmail.com
Tue Sep 18 22:18:19 EDT 2007
This is more of a "me too" than a response, but I have found that the
server does die with some regularity (at least in my case) and does
not restart, I am starting to address this now and was wondering what
is the best method, the first thing that comes to mind is some sort of
process monitor like monit or god...along the same lines, what do
people do for server boot up/reboot...my first thought is an init
script but I am sure there is a more railsy way to tie it to
application startup...I also am happy to contribute where needed
On 9/19/07, Craig Ambrose <craig at craigambrose.com> wrote:
> Hi folks,
> I've got some BackgroundRB workers to handle a long running task (triggered
> by a user) that work very well on my staging server, and I just wanted to
> check to see if anyone had any advice before I put it into production.
> When I start the worker (which performs an import), I write a record to my
> database for each import. The record gets updated by the worker to indicate
> progress, and marked as compete when finished. These tasks are idempotent,
> so I'm not concerned about attempting to do all or part of the import
> multiple times.
> It all works very nicely, but I haven't yet tested under high load, I have a
> couple of questions:
> How does the pool size work? For example, say I have a pool size of 5, and I
> try and create a 6th worker, what happens? Will it get queued and then
> created when one of the existing five is finished?
> Does the backgroundrb server crash much? If so, I could restart my workers
> based on their records in the database. Do people do this? As a manual step
> only? I could write a rake task to restart imports that I run if the server
> dies, or perhaps I could hook it in somewhere. Does backgroundRB try and
> restart itself if it fails? If so, is there a hook there I can use to
> restart my workers?
> ps: I realise BackgroundRB is not well maintained at the moment. I'm happy
> to help to some extent, as I think it's a great project, particularly in the
> area of submitting patches with tests and fixes for any problems that I
> encounter which affect my work.
> Craig Ambrose
> Backgroundrb-devel mailing list
> Backgroundrb-devel at rubyforge.org
Everything should be made as simple as possible, but not simpler. --
More information about the Backgroundrb-devel