Fix WorkQueuePolicy
retention issue
#5697
Merged
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.
The
isInterestRetention
function, which gates whether or not we runcheckInterestState
, was matching for bothInterestPolicy
andWorkQueuePolicy
.This meant that a work queue stream could throw away messages for which there was no consumer interest as the consumer ack floors for other subjects moved up.
This PR changes
isInterestRetention
to match onlyInterestPolicy
which fixes the issue. Notably this doesn't change theackMsg
behaviour which will continue to remove messages once they have been acked.Signed-off-by: Neil Twigg neil@nats.io