Auto-prune worker records older than one hour #1508

Closed
mperham opened this Issue Feb 22, 2014 · 3 comments

3 participants

@mperham
Owner

The Workers tab generates a lot of issues due to people thinking jobs are still processing when in fact Sidekiq crashed long ago and the records are stale. Prune the data to minimize those issues.

@mperham mperham closed this in 20b7a4f Feb 22, 2014
@arnodirlam

Nice to see that change! In addition to being confusing, a long list like ours (can accumulate >20k entries) and polling it appears in Redis' slow log regularly, causing short Redis timeouts of other driver connections (using redis-rb on hiredis).

@brainopia brainopia referenced this issue in brainopia/sidekiq-limit_fetch Mar 2, 2014
Closed

Limits not limiting #26

@sb4m

I have jobs who take more than 1 hour, how see them ?

@mperham
Owner

@sb4m You'll need to upgrade to Sidekiq 3.0, which is the master branch. It's not be released as a gem yet.

@spacemunkay spacemunkay referenced this issue in mhenrixon/sidekiq-unique-jobs Apr 21, 2014
Merged

Clarify README about unique expiration #36

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment