On Tue, Apr 02, 2013 at 06:18:17AM -0700, Steve Sexton wrote: > > Related to my previous message where I ended up with a process that needed > a manual reply_to_parent, I wanted to ask, what is the correct way to > shutdown ruote? I suspect that the reason I ended up losing a reply > message is because the worker process was killed and restarted at the OS > level while ruote was busy processing replies. > > I know that some database servers have the concept of a quiesce, is there > something similar in ruote? If I pause the workers does that mean that all > messages are sitting idle in the storage (which is what I want)? What > about the shutdown method on the engine?
On Tue, Apr 02, 2013 at 06:59:17AM -0700, Farrel Lifson wrote: > > Ruote::Dashboard#shutdown will propagate a shutdown call to any worker or > storate it was initialised with. Hello Steve, hello Farrel, yes, you'd better call shutdown on Engine/Dashboard. It will, as Farrel mentioned, call the shutdown methods of all the ruote components. When a ruote worker receives the shutdown call, it flags itself as "stopped" and will exit its processing loop right after handling the current "msg" or, if there is none, immediately. The processing thread is joined until it exits. "msg" documents that come after the worker shut down are kept in the storage, they'll be processed when a worker picks them up there. 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.
