Request received: RE: [resque] Creating workers on other machines (ticket #1444314)
- Tumblr Support
- 2013-02-25 @ 21:49
##- Please type your reply above this line -##
Request received: RE: [resque] Creating workers on other machines (ticket
We've received your support request (Ticket 1444314), and will get back to
you as soon as we can.<br />
In the meantime, feel free to visit our Help section where a lot of
questions have already been answered.<br />
Resque, Feb 25 04:49 pm (EST)
Sent from Windows Mail
*From:* Adam Tucker <firstname.lastname@example.org>
*Sent:* February 25, 2013 4:48 PM
*Subject:* Re: [resque] Creating workers on other machines
Wanted to clarify that your main server does *not* distribute jobs. It
holds the master list of jobs, and the workers (on whichever machine they
reside) contact the Redis store to pull jobs from.
On Monday, February 25, 2013 at 4:12 PM, Jose Cortinas wrote:
Resque uses Redis as it's main data storage and job queueing engine. That
means that any Resque processes connect to the same Redis instance that
your main server is putting jobs on, can pull jobs off of that instance and
run them. Most people have their worker's in the same directory as their
Rails app (or whatever framework you use), and therefore just deploy their
entire codebase to different machines, but don't run the application
server's on those machines, they only run the Resque workers. Redis is the
central point of communication between machines that add jobs to the queue,
and machines that pull jobs and run them.
Hope that helps,
On Feb 25, 2013, at 3:07 PM, Joseph Perenia <email@example.com> wrote:
< blockquote type="cite">
Thanks, but I guess I meant to ask how do I send jobs to another machine?
I have the main server that can distribute jobs to other machines to run
processes on. How would I accomplish that? I'm fairly new to using resque.
On Mon, Feb 25, 2013 at 1:47 PM, Spike Grobstein <firstname.lastname@example.org> wrote:
For any machine that you deploy your app to, you can run the `rake
resque:work` rake task to spawn a worker.
We have machines that we define as a `:resque` role in Capistrano and on
each of those machines, specify different collections of queues that we
pass to the above rake task.
The resque nodes do not need to be running nginx or passenger as they are
not acting as appservers.
I hope that helps.
On Feb 25, 2013, at 3:41 PM, Joseph Perenia wrote:
> How do you create workers on other machines?
This email is a service from Tumblr Support