Adapter Jobs with Resque

RhoSync uses the resque library for managing and executing asynchronous jobs. Using async jobs are especially useful when your application requires processing large amounts of data, pinging devices using the built-in push support, or you just want to perform some task that will take a long period of time.

• Async Job Types
• Running Async Jobs

Async Job Types

RhoSync supports three job types: BulkDataJob, PingJob, SourceJob

BulkDataJob

Bulk Data jobs are used by RhoSync to prepare the bulk sync data files. These jobs are automatically queued by the RhoSync application, so it is not necessary to queue them manually.

PingJob

Ping jobs are used to execute a device ping. A PingJob can be queued from anywhere in your RhoSync application (i.e. at the end of another job or adapter query method).

Example:

Resque.enqueue(
  PingJob,
  {
    "user_id" => current_user.login,
    "message" => "New products available!", 
    "badge" => 1, 
    "sources" => ['Product']
  }
)

SourceJob

Source jobs are used to execute source adapter queues asynchronously.

To make your source adapters always run asynchronously, define a queue in settings/settings.yml:

Product:
  :queue: product

Then run a resque worker so the job will execute.

Example that queues a new source adapter job manually:

Resque.enqueue(
 SourceJob,
 :query,
 APP_NAME,
 'Joe',
 'some-client-id
)

Running Async Jobs

Running RhoSync jobs requires one or more resque workers running. For example, to start one resque worker listening for all job queues:

$ cd <your rhosync app>
$ QUEUE=* rake resque:work

To start multiple workers(in this case 5):

$ cd <your rhosync app>
$ QUEUE=* COUNT=5 rake resque:workers

For more information on the options available when running resque workers, please refer to the resque readme.

If you want to run resque workers in daemon mode, we recommend using nohup, god, or monit:

$ nohup rake resque:work & &> log/resque_worker_QUEUE.log