This repository has been archived by the owner on Jan 9, 2024. It is now read-only.
fix(mem): removing kinesis batcher as possible memory leaker #826
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.
Goal
The mem leak from #825 continues.
I believe that it is likely the batch processor optimization that we had for Kinesis because it relied on timers and was polling. And because when removed, the tests no longer needed a forceExit param cause something was left open.
We will try deploying without the batch optimization since we should be well below kinesis limits for a good while.