-
-
Notifications
You must be signed in to change notification settings - Fork 3
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
Purge old keys without TTL from Redis #218
Labels
Projects
Comments
Now that we're using the native Celery AsyncResults instead of Redis pubsub, it might be a good idea to bundle this into some kind of general |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Should be easy enough, but not high priority.
We should figure out how to purge old keys that don't have a TTL. Kombu bindings to old queues with old version constraints lay around until someone cleans them up, which for most end users will be never. Deleting queues that are still in use results in those queues being created again when Celery attempts to use them. There may be some slight overhead there, but no great loss.
There are also a few stray
_kombu.binding.reply.celery.pidbox
keys. Ask Solem writes:celery/kombu#294
The keys are very small, but assuming we can just keep them forever may not be realistic. Especially if users have made their Redis instance persistent. We could:
or a combination of the three.
Here's a sample of the keys from Redis Insight:
The text was updated successfully, but these errors were encountered: