How to destroy jobs enqueued by resque workers?

Question

I'm using Resque on a rails-3 project to handle jobs that are scheduled to run every 5 minutes. I recently did something that snowballed the creation of these jobs and the stack has hit over 1000 jobs. I fixed the issue that caused that many jobs to be queued and now the problem I have is that the jobs created by the bug are still there and therefore It becomes difficult to test something since a job is added to a queue with 1000+ jobs. I can't seem to stop these jobs. I have tried removing the queue from the redis-cli using the flushall command but it didn't work. Am I missing something? coz I can't seem to find a way of getting rid of these jobs.

score 70 · Answer 1 · answered Jan 09 '13 at 16:44

70

Playing off of the above answers, if you need to clear all of your queues, you could use the following:

Resque.queues.each{|q| Resque.redis.del "queue:#{q}" }

answered Jan 09 '13 at 16:44

shedd

4,198
4
33
42

score 51 · Accepted Answer · edited Jul 12 '13 at 10:09

51

If you pop open a rails console, you can run this code to clear out your queue(s):

queue_name = "my_queue"
Resque.redis.del "queue:#{queue_name}"

edited Jul 12 '13 at 10:09

alony

10,725
3
39
46

answered May 04 '11 at 13:35

Dylan Markow

123,080
26
284
201

4

As found in @denmarkin's answer below, use Resque.redis.del instead of Resque.redis.delete – James P McGrath Nov 03 '11 at 04:08

score 36 · Answer 3 · edited Oct 08 '15 at 07:31

36

Resque already has a method for doing this - try Resque.remove_queue(queue_name) (see the documentation here). Internally it performs Resque.redis.del(), but it also does other cleanup, and by using an api method (rather than making assumptions about how resque works) you'll be more future-proof.

edited Oct 08 '15 at 07:31

Richard

436
3
8

answered Apr 22 '13 at 00:36

iainbeeston

1,851
1
21
20

Using the Resque API is a better approach – grant Jun 24 '16 at 20:07

score 14 · Answer 4 · answered Mar 31 '15 at 10:05

14

This is what works now:

Resque.remove_queue("...")

answered Mar 31 '15 at 10:05

vladCovaliov

4,333
2
43
58

Yep, that seems to be the right way to do this: http://www.rubydoc.info/gems/resque/1.27.4/Resque#remove_queue-instance_method – jwadsack Oct 27 '17 at 16:10

score 14 · Answer 5 · answered Sep 20 '11 at 11:03

14

Updated rake task for clearing (according to latest redis commands changes): https://gist.github.com/1228863

answered Sep 20 '11 at 11:03

denmarkin

233
3
10

score 5 · Answer 6 · answered Aug 14 '18 at 12:58

It's safer and bulletproof to use the Resque API rather than deleting everything on the Resque's Redis. Resque does some cleaning in the inside.

If you want to remove all queues and associated enqueued jobs:

Resque.queues.each {|queue| Resque.remove_queue(queue)}

The queues will be re-created the next time a job is enqueued.

Documentation

score 4 · Answer 7 · answered Apr 01 '16 at 19:50

Enter redis console:

redis-cli

List databases:

127.0.0.1:6379> KEYS *
 1) "resque:schedules_changed"
 2) "resque:workers"
 3) "resque:queue:your_overloaded_queue"

"resque:queue:your_overloaded_queue" - db which you need.

Then run:

DEL resque:queue:your_overloaded_queue

Or if you want to delete specified jobs in queue then list few values from db with LRANGE command:

127.0.0.1:6379> LRANGE resque:queue:your_overloaded_queue 0 2
1) "{\"class\":\"AppClass\",\"args\":[]}"
2) "{\"class\":\"AppClass\",\"args\":[]}"
3) "{\"class\":\"AppClass\",\"args\":[]}"

Then copy/paste one value to LREM command:

127.0.0.1:6379> LREM resque:queue:your_overloaded_queue 5 "{\"class\":\"AppClass\",\"args\":[]}"
(integer) 5

Where 5 - number of elements to remove.

Redis recommends that you [not run `KEYS *` on a production database](https://redis.io/commands/keys) as it scans the entire set of keys and locks all records. This could adversely affect your background workers on a very busy system. — jwadsack, Nov 14 '17 at 04:48

How to destroy jobs enqueued by resque workers?

7 Answers7

Linked