fix(redis): prevent memory leak by deleting acknowledged stream messages, added test coverage for message deletion behaviour #2232
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.
Description
This PR implements automatic deletion of Redis Stream messages after acknowledgment to prevent memory accumulation in long-running FastStream applications.
Problem: Redis Stream messages were only being acknowledged (XACK) but never deleted from the stream, causing Redis memory to grow indefinitely as processed messages accumulated.
Solution: Added
XDEL
call immediately afterXACK
in the_RedisStreamMessageMixin.ack()
method to automatically remove messages from the stream after successful processing.Impact: This changes Redis Streams behavior from persistent event log to message queue semantics, preventing memory leaks while maintaining backward compatibility for typical use cases.
Fixes #2223
Type of change
Please delete options that are not relevant.
Checklist
scripts/lint.sh
shows no errors)scripts/test-cov.sh
scripts/static-analysis.sh