Hi John,
Indeed, I wanted to "protect" ruote behind a queuing system (Sidekiq or
Ruote) since the few tests (in terms of charge) let me think that ruote
were not designed to handle 20 processes/seconds. What do you guys usually
do?
Anyway, concerning the queuing system between ruote and its participants,
I'd like to use amqp.
I've generate my participant with daemon-kit, it's up and waiting, but my
processes are crashing with:
{"fei":{"engine_id":"engine","wfid":"20130319-1535-keguteya-dejujuha","subid":"e92c906320eeaa2e14da2191531fdba9","expid":"0_0_0"},"at":"2013-03-19
15:35:16.406278 UTC","class":"RuntimeError","message":"#<RuntimeError:
eventmachine not initialized: evma_connect_to_server>","trace":"
/opt/boxen/rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/gems/eventmachine-0.12.10/lib/eventmachine.rb:714:
in
`connect_server'\n/opt/boxen/rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/gems/eventmachine-0.12.10/lib/eventmachine.rb:714:
in
`bind_connect'\n/opt/boxen/rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/gems/eventmachine-0.12.10/lib/eventmachine.rb:692:
in
`connect'\n/opt/boxen/rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/gems/amq-client-0.9.12/lib/amq/client/async/adapters/event_machine.rb:45:
in
`connect'\n/opt/boxen/rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/gems/amqp-0.9.7/lib/amqp/client.rb:39:in
`connect'\n/opt/boxen/rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/gems/amqp-0.9.7/lib/amqp/connection.rb:214:
in
`connect'\n/opt/boxen/rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/gems/ruote-amqp-2.3.0.1/lib/ruote/amqp/participant.rb:297:in
`amqp_connect'\n/opt/boxen/rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/gems/ruote-amqp-2.3.0.1/lib/ruote/amqp/participant.rb:307:
in
`channel'\n/opt/boxen/rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/gems/ruote-amqp-2.3.0.1/lib/ruote/amqp/alert_participant.rb:142:in
`queue'\n/opt/boxen/rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/gems/ruote-amqp-2.3.0.1/lib/ruote/amqp/alert_participant.rb:118:
in
`on_workitem'\n/opt/boxen/rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/gems/ruote-2.3.0.2/lib/ruote/svc/dispatch_pool.rb:210:in
`block in
participant_send'\n/opt/boxen/rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/gems/ruote-2.3.0.2/lib/ruote/svc/dispatch_pool.rb:206:
in
`each'\n/opt/boxen/rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/gems/ruote-2.3.0.2/lib/ruote/svc/dispatch_pool.rb:206:in
`participant_send'\n/opt/boxen/rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/gems/ruote-2.3.0.2/lib/ruote/svc/dispatch_pool.rb:79:
in
`do_raw_dispatch'\n/opt/boxen/rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/gems/ruote-2.3.0.2/lib/ruote/svc/dispatch_pool.rb:95:in
`do_dispatch'\n/opt/boxen/rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/gems/ruote-2.3.0.2/lib/ruote/svc/dispatch_pool.rb:62:
in
`dispatch'\n/opt/boxen/rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/gems/ruote-2.3.0.2/lib/ruote/svc/dispatch_pool.rb:46:in
`handle'\n/opt/boxen/rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/gems/ruote-2.3.0.2/lib/ruote/worker.rb:396:
in
`process'\n/opt/boxen/rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/gems/ruote-2.3.0.2/lib/ruote/worker.rb:210:in
`process_msgs'\n/opt/boxen/rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/gems/ruote-2.3.0.2/lib/ruote/worker.rb:258:
in
`step'\n/opt/boxen/rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/gems/ruote-2.3.0.2/lib/ruote/worker.rb:109:in
`run'\n/opt/boxen/rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/gems/ruote-2.3.0.2/lib/ruote/worker.rb:120:in
`block in
run_in_thread'","details":null,"deviations":null,"tree":["participant",{"waiting_subpictures_upload":null},[]],"type":"errors","_id":"err_0_0_0!e92c906320eeaa2e14da2191531fdba9!20130319-1535-keguteya-dejujuha","msg":{"fei":{"engine_id":"engine","wfid":"20130319-1535-keguteya-dejujuha","subid":"e92c906320eeaa2e14da2191531fdba9","expid":"0_0_0"},"participant_name":"waiting_subpictures_upload","participant":["Ruote::Amqp::AlertParticipant",{"queue":"work1"}],"workitem":{"fields":{"params":{"waiting_subpictures_upload":null},"dispatched_at":"2013-03-19
15:35:16.404416
UTC"},"wf_name":"receipt_workflow","wf_revision":null,"wf_launched_at":"2013-03-19
15:35:16.386047
UTC","sub_wf_name":"receipt_workflow","sub_wf_revision":null,"sub_wf_launched_at":"2013-03-19
15:35:16.386082
UTC","fei":{"engine_id":"engine","wfid":"20130319-1535-keguteya-dejujuha","subid":"e92c906320eeaa2e14da2191531fdba9","expid":"0_0_0"},"participant_name":"waiting_subpictures_upload","re_dispatch_count":0},"type":"msgs","_id":"65332!70139251295520!2013-03-19!1363707316.401815!003","action":"dispatch","put_at":"2013-03-19
15:35:16.401861 UTC"},"_rev":"1","put_at":"2013-03-19 15:35:16.406923 UTC"}
Any hint :s ?
Regards,
Ludovic
On Monday, March 18, 2013 10:56:31 PM UTC+1, John Mettraux wrote:
>
>
> Hello,
>
> I have no Sidekiq experience, but I can read.
>
> On Mon, Mar 18, 2013 at 02:46:16PM -0700, Ludovic wrote:
> >
> > Is anyone has a feedback to share about using Ruote with Sidekiq?
> > I'm naively trying to "bundle exec sidekiq -r ruote.rb" with a ruote.rb
> > containing the following lines:
>
> What is this "bundle exec sidkiq -r whatever.rb" supposed to achieve? I
> can't
> find it mentioned in the documentation of Sidekiq (didn't search too long
> though).
>
> From ten thousands of kilometers away, it seems like you're trying to tell
> Sidekiq to run ruote... Wouldn't it be the other way around? Ruote should
> hand work via some participant to Sidekiq (and there should be a way for
> Sidekiq jobs to communicate back to ruote, ruote-amqp would be a good
> model
> to follow then).
>
>
> Best regards,
>
> --
> John Mettraux - http://lambda.io/jmettraux
>
--
--
you received this message because you are subscribed to the "ruote users" group.
to post : send email to [email protected]
to unsubscribe : send email to [email protected]
more options : http://groups.google.com/group/openwferu-users?hl=en
---
You received this message because you are subscribed to the Google Groups
"ruote" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
