没有一个这些解决办法对我有利,我仍然会看到这一点。

0 out of 10 Workers Working

最后,这为我扫清所有工人的工作:

Resque.workers.each {|w| w.unregister_worker}

In your console:

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

否则,你会试图欺骗他们,就像他们去除他们那样做的:

Resque::Worker.working.each {|w| w.done_working}

http://www.ohchr.org。

许多人已经放弃了这一答案,我感到重要的是,人们必须尝试以 ha方式解决问题,而不要让工人坐在一旁,而上述法典删除了问题。 如果你乐于 f,那么冷却。

You probably have the resque gem installed, so you can open the console and get current workers

Resque.workers

工人名单

#=> [#<Worker infusion.local:40194-0:JAVA_DYNAMIC_QUEUES,index_migrator,converter,extractor>]

选择工人和prune_dead_workers,例如,第一例

Resque.workers.first.prune_dead_workers

除了用哈戈夫作答外,我只想能够找到一些时间的未婚工人。 下面的法典只剩300秒(5分钟)。

Resque.workers.each {|w| w.unregister_worker if w.processing[ run_at ] && Time.now - w.processing[ run_at ].to_time > 300}

我一直在收集与雷克相关的雷克任务,我也将此补充到:。

开始在 最近。 它不是解决如何安置 st工的问题,而是解决 res/being的问题,因此,我觉得,这可能有助于处于这种边缘的人。 From README:

I ran into this issue and started down the path of implementing a lot of the suggestions here. However, I discovered the root cause that was creating this issue was that I was using the gem redis-rb 3.3.0. Downgrading to redis-rb 3.2.2 prevented these workers from getting stuck in the first place.

I ve cleared them out from redis-cli directly. Luckily redistogo.com allows access from environments outside heroku. Get dead worker ID from the list. Mine was

55ba6f3b-9287-4f81-987a-4e8ae7f51210:2

Run this command in redis directly.

del "resque:worker:55ba6f3b-9287-4f81-987a-4e8ae7f51210:2:*"

你们可以监测重新布局,看看看它在幕后做什么。

redis xxx.redistogo.com> MONITOR
OK
1380274567.540613 "MONITOR"
1380274568.345198 "incrby" "resque:stat:processed" "1"
1380274568.346898 "incrby" "resque:stat:processed:c65c8e2b-555a-4a57-aaa6-477b27d6452d:2:*" "1"
1380274568.346920 "del" "resque:worker:c65c8e2b-555a-4a57-aaa6-477b27d6452d:2:*"
1380274568.348803 "smembers" "resque:queues"

Second last line deletes the worker.

In resque 2.0.0, here s one way that seems to work to remove only actually appearantly-dead workers in resque 2.0.0:

Resque::Worker.all_workers_with_expired_heartbeats.each { |w| w.unregister_worker }

我不是一位专家,他们可以做得更好,或者会遇到问题。 我只是想说这一点。

这似乎将寄回“智能”的工人从resque workers list移走的时间大大超过预期。

如果母体工人处于“经营”状态,那么,在“失败”的工作岗位上将创造与原产地相应的新条目。

我也 st了/拖了工人,或者我说了工作,因为工人实际上仍然在那里,而且打上了罚款,这打上了 st的工序。

我选择了残酷的杀戮解决办法,因为有超过5名未成年人,通过双手套,然后工人就在下游,一切照旧。

查阅我的发言稿:https://gist.github.com/jobwat/5712437。

如果你使用更新的Resque版本,那么当内部的APIC改变时,你需要使用以下指挥系统。

Resque::WorkerRegistry.working.each {|work| Resque::WorkerRegistry.remove(work.id)}

This avoids the problem as long as you have a resque version newer than 1.26.0:

resque: env QUEUE=foo TERM_CHILD=1 bundle exec rake resque:work

不要让目前从事的工作结束。

如果你使用Docker,你也可以使用这一指挥:

<id> 是工人补贴。

docker stop <id>

docker start <id>