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.
Not cleaning up the sessions causes quite a big memory leak which in effect causes OOMKilled
It's an alternative approach to #3163 in which, instead of keeping the timestamp of the last usage, we add cleanup into the flow.
Note that I'm 100% we won't have some corner cases, like segment was returned with a delay and now we cannot find the session. Saying that, it should not crash anything. Also, I did quite a lot of local dev chain tests, so I think it should work fine.
My plan is to get it merged and then deploy to one region for some time to see if we see any regression.