Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Removing "uniquejobs" hash? #213

Closed
lephyrius opened this issue Mar 5, 2017 · 3 comments
Closed

Removing "uniquejobs" hash? #213

lephyrius opened this issue Mar 5, 2017 · 3 comments

Comments

@lephyrius
Copy link

lephyrius commented Mar 5, 2017 •
edited
Loading

I noticed that I had a memory OOM error in redis. So I investigated what was causing it and I found that the "uniquejobs" key was extremely large. (like 98% of our redis)
So...
Is this a bug?
Have I misunderstood how this works? Have I broken anything by removing the hash?
Do I need some kind of cleaner because right now it doesn't seem to cleanup by itself?
@wendelscardua
Copy link

@lephyrius it seems to be related to #200 , and indirectly to #206 , so it should be fixed in the next release (as this fix is yet to be released, I've resigned myself to using the master branch version for now - gem 'sidekiq-unique-jobs', github: 'mhenrixon/sidekiq-unique-jobs')

@mhenrixon
Copy link
Owner

We should remove jobs better in version 5.0.0. Feel free to reopen an issue if that is not the case!

@mhenrixon
Copy link
Owner

You can also clear the hash by running bundle exec jobs expire

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mhenrixon @lephyrius @wendelscardua