jayniz/resque-loner — Issue #18: Sometimes Loner "locks" a given job
Author: marcgg
Created: 2012-01-17 18:53:41+00:00
State: open

Hi!

First of thanks for the great gem, I've been using it extensively on a large scale application, but recently I'm seeing some issue.

It seems that sometimes, even though the job is performed correctly, loner will not remove the lock.
It appears sporadically and I don't see a pattern for it.

The thing is that I use resque to process hundreds of jobs per seconds, so I was wondering if you saw a point in loner where this could happen. For instance if there are too many access at once etc.

I kind of "fixed" the problem by adding a TTL, but some queues can't afford to be locked for more than a couple of minutes. I decided to remove loner on these kind of queues, but I'd rather keep it for security and get loner to work perfectly.

If you have any ideas regarding this or if you saw the same behavior somewhere it would interest me a lot.

Thanks