Not all sidekiq:sidekiq_unique keys are removed from Redis about sidekiq-unique-jobs HOT 2 CLOSED

Interesting, does anyone know what is going on?

On Wed, Mar 5, 2014 at 11:38 PM, Zhaohan Weng [email protected]:

I see the same thing, but on dev machine as well.
all I have is a simple test worker

class CountWorker
include Sidekiq::Worker
sidekiq_options retry: 3, queue: 'counter'
sidekiq_options unique: true, unique_job_expiration: 60

sidekiq_retries_exhausted do |msg|
# something wrong
end

def perform(id)
sleep(10)
end
end

and I have a loop try to schedule this worker CountWorker.perform_at(10.seconds,
1)
every second, only the first one is scheduled. In theory, the second one
should be scheduled after 10 seconds, since the first one will be finished
(sleep 10). But instead, the second one is only queued after 60 second.

Reply to this email directly or view it on GitHubhttps://github.com//issues/31#issuecomment-36803532
.

from sidekiq-unique-jobs.

An old sidekiq process was still taking jobs from the queue, and failing them. Since this process did not care to remove the unique key from redis, this resulted in unexpected behavior.

from sidekiq-unique-jobs.