[PATCH conductor] RM 3181 - delayed_job support - revised
Jason Guiditta
jguiditt at redhat.com
Mon May 7 16:40:17 UTC 2012
On 04/05/12 17:22 -0700, Richard Su wrote:
>rev2 - Rebased. Incorporated Jay's feedback; to leave db migration
>the same as there are no changes and to update Gemfile.lock.
>
>Add delayed_job version 2.1.4 back into our environment: db migration,
>initializer, and script.
>
>Created systemd configuration file. Spec file installs config file into
>/lib/systemd/system.
>
>The service is named conductor-delayed_job and can be controlled through
>either of these two commands:
>"systemctl start/stop/status conductor-delayed_job.service"
>"service conductor-delayed_job start/stop/status"
>
>Service brings up 2 workers to process the queue.
Actually, as second look at the log may have answered my 2nd question.
I think it actually proves you have 2 queues set up:
MyTestJob completed after 0.0165
2012-05-07T12:33:45-0400: [Worker(delayed_job.0 host:lenovo.jay.g
pid:10624)]
2 jobs processed at 17.1702 j/s, 0 failed ...
2012-05-07T12:33:45-0400: [Worker(delayed_job.1 host:lenovo.jay.g
pid:10631)]
MyTestJob completed after 0.0165
2012-05-07T12:33:45-0400: [Worker(delayed_job.1 host:lenovo.jay.g
pid:10631)]
98 jobs processed at 17.7766 j/s, 0 failed ...
as there is one list for 2 jobs, and another for 98.
-j
More information about the aeolus-devel
mailing list