-
-
Notifications
You must be signed in to change notification settings - Fork 701
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
Archived tasks that are trimmed from the set are deleted #743
Archived tasks that are trimmed from the set are deleted #743
Conversation
Depends on #441 |
local extra = redis.call("ZRANGE", KEYS[4], 0, -ARGV[5]) | ||
if #extra > 0 then | ||
for _, id in ipairs(extra) do | ||
redis.call("DEL", KEYS[9] .. id) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ideally, we need to raise the maxArchiveSize or make it settable before calling delete here. In a scenario where tasks are failing and reaching max retries fast, it will just keep clearing them from the queue before allowing for manual intervention.
I see it is being tracked in #534 already :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, changes look good to me. I have left a suggestion.
When will this pull request be merged? |
I will try and work on the suggestion in the next few weeks. |
@kamikazechaser nvm it took 3 seconds to change, confirmed the tests I added still pass. Anything else you need changed? |
No, Thanks! |
When will 0.25.0 be published? 9999 archived task made me crazy. |
Solves the issue outlined in: #730
You can confirm the test case/fix is working by deleting lines: 852/860 in rdb.go of the fix branch to observe the old failure.