ruby on rails - Resque worker not responding to signals -


I am using 1.25.2 version of the rus in a Rail app.

I tried to do these as examples of pause_processing and its reverse unpause_processing of Resque :: Worker class of all workers But me Resque.workers . However, the workers still continue the process of new jobs dynamically added in any queue. Every worker true

is not sure if I really want to go to the state with example.paused I can control the workers running in the background. / P>

As far as I can understand pause_processing , unpause_processing and shutdown

Am I missing something trivial or is there another way to manage workers?

That's because you are calling this method The workers are in a position to modify completely on a different example. As you all do, it determines the value of a variable variable. When you call Resque.workers , you get examples of all workers but not an example of a worker running in a separate process. Rescue does not allow you to remotely modify the status of a moving worker. If you want to change the status of a resque worker from outside, you should interact with the signs. If you are just calling the methods, then you are not sending a signal.

Comments

Popular posts from this blog

Java - Error: no suitable method found for add(int, java.lang.String) -

java - JPA TypedQuery: Parameter value element did not match expected type -

c++ - static template member variable has internal linkage but is not defined -