Celery: cleanup pidbox keys
#10002
Merged
Celery: cleanup pidbox keys
#10002
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Simple task to remove `pidbox` keys older than 15 minutes. This is a workaround to avoid Redis OOM for now. We will need to find out a better solution here. There is an upstream issue opened that we should check in the near future and probably remove this workaround: celery/celery#6089
humitos
force-pushed
the
humitos/cleanup-pidbox-objects
branch
from
28f1128 to
b97f825
Compare
humitos
commented
Feb 9, 2023
ericholscher
approved these changes
Feb 9, 2023
`app.backend.client` is not working anymore since we are not using a backend result anymore.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Simple task to remove
pidboxkeys older than 15 minutes. This is a workaround to avoid Redis OOM for now.We will need to find out a better solution here. There is an upstream issue opened that we should check in the near future and probably remove this
workaround: celery/celery#6089
Related: https://github.com/readthedocs/readthedocs-ops/issues/1260