Backgroundrb devel - Feb 2008 - query queued jobs

Hi all,

I don''t have any status logging setup for my workers, but some of them
have turned out to be rather longer jobs than I''d anticipated (like 24
hours and still going). So I was wondering if there''s any way to query
the server for a list of queued jobs to see how much backup there is.
I''d think this could be independent of actual worker statuses, since
the server must be holding a queue regardless of the internals of the
workers themselves. FWIW, I''ve been queuing all my workers with
#ask_work.

Thanks,
Ian

Your timing is auspicious. I just coded up a status method for the cache
clearing worker I created for my company''s CMS app. I received the
green
light from my manager to donate the code to the project; however, I
still have a bit testing and perfecting to do. Expect a check-in by the
end of the month.

George Feil | Senior Software Engineer
office 415.295.8524 | fax 415.295.8580
www.realgirlsmedia.com
www.divinecaroline.com
> -----Original Message-----
> From: backgroundrb-devel-bounces at rubyforge.org
[mailto:backgroundrb-devel-
> bounces at rubyforge.org] On Behalf Of Ian Smith-Heisters
> Sent: Wednesday, February 20, 2008 9:42 AM
> To: backgroundrb-devel at rubyforge.org
> Subject: [Backgroundrb-devel] query queued jobs
> 
> Hi all,
> 
> I don''t have any status logging setup for my workers, but some of
them
> have turned out to be rather longer jobs than I''d anticipated
(like 24
> hours and still going). So I was wondering if there''s any way to
query
> the server for a list of queued jobs to see how much backup there is.
> I''d think this could be independent of actual worker statuses,
since
> the server must be holding a queue regardless of the internals of the
> workers themselves. FWIW, I''ve been queuing all my workers with
> #ask_work.
> 
> Thanks,
> Ian
> _______________________________________________
> Backgroundrb-devel mailing list
> Backgroundrb-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/backgroundrb-devel

Cool, great to hear. Maybe my queue will have gotten through this job by then ;)

On 2/20/08, George Feil <gfeil at realgirlsmedia.com>
wrote:
> Your timing is auspicious. I just coded up a status method for the cache
>  clearing worker I created for my company''s CMS app. I received
the green
>  light from my manager to donate the code to the project; however, I
>  still have a bit testing and perfecting to do. Expect a check-in by the
>  end of the month.
>
>  George Feil | Senior Software Engineer
>  office 415.295.8524 | fax 415.295.8580
>  www.realgirlsmedia.com
>  www.divinecaroline.com
>
>
>  > -----Original Message-----
>  > From: backgroundrb-devel-bounces at rubyforge.org
>  [mailto:backgroundrb-devel-
>  > bounces at rubyforge.org] On Behalf Of Ian Smith-Heisters
>  > Sent: Wednesday, February 20, 2008 9:42 AM
>  > To: backgroundrb-devel at rubyforge.org
>  > Subject: [Backgroundrb-devel] query queued jobs
>  >
>  > Hi all,
>  >
>  > I don''t have any status logging setup for my workers, but
some of them
>  > have turned out to be rather longer jobs than I''d
anticipated (like 24
>  > hours and still going). So I was wondering if there''s any
way to query
>  > the server for a list of queued jobs to see how much backup there is.
>  > I''d think this could be independent of actual worker
statuses, since
>  > the server must be holding a queue regardless of the internals of the
>  > workers themselves. FWIW, I''ve been queuing all my workers
with
>  > #ask_work.
>  >
>  > Thanks,
>  > Ian
>
> > _______________________________________________
>  > Backgroundrb-devel mailing list
>  > Backgroundrb-devel at rubyforge.org
>  > http://rubyforge.org/mailman/listinfo/backgroundrb-devel
>
>

Currently, we only have all_worker_info and worker_info for queering
runtime information of workers.
I think, we can pimp up information provided by these methods.



On Wed, Feb 20, 2008 at 11:51 PM, Ian Smith-Heisters
<heisters at greenriver.org> wrote:
> Cool, great to hear. Maybe my queue will have gotten through this job by
then ;)
>
>
>
>  On 2/20/08, George Feil <gfeil at realgirlsmedia.com> wrote:
>  > Your timing is auspicious. I just coded up a status method for the
cache
>  >  clearing worker I created for my company''s CMS app. I
received the green
>  >  light from my manager to donate the code to the project; however, I
>  >  still have a bit testing and perfecting to do. Expect a check-in by
the
>  >  end of the month.
Thats cool. Looking forward.

ah, cool, all_worker_info looks like it''ll help out. This
doesn''t
appear to be mentioned anywhere on http://backgroundrb.rubyforge.org/

Thanks!

On 2/20/08, hemant <gethemant at gmail.com> wrote:
> Currently, we only have all_worker_info and worker_info for queering
>  runtime information of workers.
>  I think, we can pimp up information provided by these methods.
>
>
>
>
>  On Wed, Feb 20, 2008 at 11:51 PM, Ian Smith-Heisters
>  <heisters at greenriver.org> wrote:
>  > Cool, great to hear. Maybe my queue will have gotten through this job
by then ;)
>  >
>  >
>  >
>  >  On 2/20/08, George Feil <gfeil at realgirlsmedia.com> wrote:
>  >  > Your timing is auspicious. I just coded up a status method for
the cache
>  >  >  clearing worker I created for my company''s CMS app. I
received the green
>  >  >  light from my manager to donate the code to the project;
however, I
>  >  >  still have a bit testing and perfecting to do. Expect a
check-in by the
>  >  >  end of the month.
>
>
> Thats cool. Looking forward.
>

Hi, I had the problem of running different BackgrounDRB processes with 
different environments on the same box. BackgrounDRB does not support 
that, so I added a little bit of code. I opened ticket #80 on devjavu 
with the patch attached.

* script/backgroundrb now supports cli parameters

    * -h for help
    * -e to choose an environment

* moved configuration handling into lib/bdrb_config.rb

    if there is an entry in backgroundrb.yml with the environment name
    that entry is merged back into the config, eg:

---
:development:
  :backgroundrb:
    :port: 11111
:production:
  :backgroundrb:
    :port: 11113

:backgroundrb:
  :ip: localhost
  :port: 11006

        if you run this under development port will be 11111, under
        production port will be 11113 (this is pretty cool, you can add
        config instructions depending on the environment, even schedules:)

* the PID files goes into tmp/pids/

* PID and LOG file names now include the port for differentiation

Hope this improves BackgrounDRB a little bit.
-alex

On Thu, Feb 21, 2008 at 2:30 PM, Alex Peuchert
<rubyonrails-ug at peuchert.de> wrote:
> Hi, I had the problem of running different BackgrounDRB processes with
>  different environments on the same box. BackgrounDRB does not support
>  that, so I added a little bit of code. I opened ticket #80 on devjavu
>  with the patch attached.
>
>  * script/backgroundrb now supports cli parameters
>
>     * -h for help
>     * -e to choose an environment
>
>  * moved configuration handling into lib/bdrb_config.rb
>
>     if there is an entry in backgroundrb.yml with the environment name
>     that entry is merged back into the config, eg:
>
>  ---
>  :development:
>   :backgroundrb:
>     :port: 11111
>  :production:
>   :backgroundrb:
>     :port: 11113
>
>  :backgroundrb:
>   :ip: localhost
>   :port: 11006
>
>         if you run this under development port will be 11111, under
>         production port will be 11113 (this is pretty cool, you can add
>         config instructions depending on the environment, even schedules:)
>
>  * the PID files goes into tmp/pids/
>
>  * PID and LOG file names now include the port for differentiation
>
>  Hope this improves BackgrounDRB a little bit.

Awesome. I am having a look and commit them accordingly. Also, as a
rule, you are qualified for commit access, so create an account on
gitorious and let me know your login handle.

http://gitorious.org/projects/backgroundrb

Hi BackgroundRb users!

I''ve been away for a while, now. And after having a look at 
backgroundrb, I found that there is a repository of backgroundrb at 
github.com. Is this the place to develop, now?

Regards, Alexander

On Wed, May 28, 2008 at 7:09 PM, Alex <rubyonrails-ug at peuchert.de>
wrote:
> Hi BackgroundRb users!
>
> I''ve been away for a while, now. And after having a look at
backgroundrb, I
> found that there is a repository of backgroundrb at github.com. Is this the
> place to develop, now?
>
Hi Alex,

Yes, I have moved backgroundrb repo to github. I was having various
issues with gitorious and hence the reason. I will give you the commit
bits, hang on.