[FIXED] THW: ExpireTasks in full wheel #7070
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.
If a TTL was used that's larger than
wheelMask * time.Second ≃ 1h 8m
, it could take double the time for those messages to expire. This was because we'd only loop through the wheel between astartPos
andexitPos
. Which works if we only need to loop over a smaller part of the wheel, but doesn't work if we should loop over it in its entirety.We can simply always loop over the full wheel, since if we do end up expiring anything we call into
hw.updateLowestExpires()
which loops over the full wheel already anyway.Signed-off-by: Maurice van Veen github@mauricevanveen.com