-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
State store and/or DynamoDB client not stopped when stopConsumer() called #337
Comments
Just to experiment I tried also adding
The dynamodb-client retry does eventually stop if I let it sit there for a few minutes, but the leaks still don't go away at that point either. Is there anything else I need to be sure to close/destroy to make sure lifion kinesis cleans up after itself? |
HI @GoldFlsh, thanks for reporting this. Let me take a look. I'll comment back ASAP. |
I'm actually seeing the same behavior with the kinesis-client, too now. I updated to the latest version of lifion-kinesis cause I realized I was using a slightly older version.
This is after running
|
Hello, I am running into an issue where when I run my application in jest connecting to a local instance of kinesis (re: Kinesalite). However, the issue I am seeing is that it detects open handles even when
stopConsumer()
is called before the end of a test.I've isolated this just to when lifion-kinesis is set to consume, so I know the issue is when using this library.
My test is set up in this way ->
beforeAll(start kinesalite/dynalite) -> test(startConsumer -> stop Consumer) -> afterAll(stop kinesalite/dynalite)
When I run with https://github.com/Raynos/leaked-handles it checks what's still open and I get the following output -
The text was updated successfully, but these errors were encountered: