Questions tagged [resque]

Resque (pronounced like "rescue") is a Redis-backed library for creating background jobs, placing those jobs on multiple queues, and processing them later.

Background jobs can be any Ruby class or module that responds to perform. Your existing classes can easily be converted to background jobs or you can create new classes specifically to do work. Or, you can do both.

Resque is heavily inspired by DelayedJob (which rocks) and comprises three parts:

A Ruby library for creating, querying, and processing jobs A Rake task for starting a worker which processes jobs A Sinatra app for monitoring queues, jobs, and workers. Resque workers can be distributed between multiple machines, support priorities, are resilient to memory bloat / "leaks," are optimized for REE (but work on MRI and JRuby), tell you what they're doing, and expect failure.

Resque queues are persistent; support constant time, atomic push and pop (thanks to Redis); provide visibility into their contents; and store jobs as simple JSON packages.

The Resque frontend tells you what workers are doing, what workers are not doing, what queues you're using, what's in those queues, provides general usage stats, and helps you track failures.

For the backstory, philosophy, and history of Resque's beginnings, please see the blog post.

1074 questions
-1
votes
2 answers

Rails Resque Concurrency

My application is processing jobs with Resque.enqueue I am starting the worker with rake resque:work QUEUE='converter' To my understanding, in order to start 2 workers to process 2 requests for the same queue concurrently, I can start another worker…
GavinBelson
  • 2,514
  • 25
  • 36
-1
votes
1 answer

Are spies an appropriate approach to see if Resque methods are being fired?

While simple coverage is reporting this as 100% covered I am not satisfied. The spec marked as focus I would like to confirm that all of the Resque methods are being fired. Is a spy or a double the right approach for this? Spec describe 'resque…
Chris Hough
  • 3,389
  • 3
  • 41
  • 80
-1
votes
1 answer

Heroku, Rails, Resque, Redis: All jobs failing because of Errno::ETIMEDOUT

I have a rails app on heroku that uses Resque.enqueu to schedule background jobs using Redis and redistogo. Jobs used to work normally but I notice now that they have all been failing for some time (a few weeks, 100% of jobs). The error I…
Jackson Cunningham
  • 4,973
  • 3
  • 30
  • 80
-1
votes
1 answer

Config Resche schedule to delay sending mail in specific time

SO sorry if this is a duplicate, I tried searching for this but wasnt sure what search terms to use and didnt really find anything I'm currently research on how to set up a schedule of job-to-do when a server start on my application. The function I…
-1
votes
1 answer

How to kill background job in resque like the gem sidekiq

I use rescue gem for managing my background jobs, I want get the handle id after creating an new background job, Then I can kill the background job anytime with the handle id. But I couldn’t get it with resque, it seems there is no way to delete any…
newBike
  • 14,385
  • 29
  • 109
  • 192
-1
votes
1 answer

Resque job not being queued according to resque_spec but is available in job list

I have the following test in rspec it "should add the item to the resque queue" do post :run, id: report.id resque_job = Resque.peek(:default_queue) expect(resque_job).to be_present puts "Job is #{resque_job}" …
pbattisson
  • 1,230
  • 2
  • 10
  • 24
-1
votes
1 answer

Heroku gem api scaling workers response 422 Unprocessable Entity

I am using the gem "heroku-resque-auto-scale" to scale workers. In resque I can see all jobs are failed: RestClient::UnprocessableEntity Error 422 Unprocessable Entity Here is the full error log:…
Rails beginner
  • 14,321
  • 35
  • 137
  • 257
-1
votes
1 answer

Hundreds of Simultaneous Jobs: Node or PHP/nginx

I am implementing a Job queueing system that should be easy to scale (by adding more servers) and has to handle hundreds to thousands of simultaneous job processes at any one time. The load can change drastically over time. Each job involve…
Nyxynyx
  • 61,411
  • 155
  • 482
  • 830
-2
votes
1 answer

rails app using resque .i am always getting SystemExit Error exit error as falied jobs when viewing in resque web interface.how to resolve?

i have class Compile in /lib whose method i run in the resque class in app/workers the resque class is this $:.unshift(Rails.root.join("lib")) require "Compile.rb" class CC @queue= :results_queue …
Ashesh Vidyut
  • 119
  • 2
  • 9
1 2 3
71
72