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.

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

The finished jobs list (rq:finished:) never gets cleaned up #519

Closed
cosminstefanxp opened this issue Apr 23, 2015 · 2 comments · Fixed by #534
Closed

The finished jobs list (rq:finished:) never gets cleaned up #519

cosminstefanxp opened this issue Apr 23, 2015 · 2 comments · Fixed by #534

Comments

@cosminstefanxp
Copy link
Contributor

First of all, great job with the project. It's awesome.

Now, to get to my problem. I'm using RQ in a high throughput system, with hundreds of thousands of jobs/day. Even though we have a result_ttl set up and the keys for the jobs themselves get cleared out, the rq:finished:low ZSET which contains ids of finished jobs does not seem to be cleared. As a result, since we put the system in production (4 days ago), it has grown to ~3M entries and keeps growing. This is starting to use a lot of memory and has a visible effect on the performance.

@nvie

@selwin
Copy link
Collaborator

selwin commented May 9, 2015

You could cleanup this by calling finished_job_registry.cleanup(). We should also create a rq cleanup management script that can be called periodically to run cleanup jobs of all registries.

@selwin
Copy link
Collaborator

selwin commented May 23, 2015

@cosminstefanxp please see #534 , this PR should address this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants