Skip to content
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

KinesisProducer is not correctly destroying callbackCompletionExecutor #224

Closed
xbcratos opened this issue Sep 28, 2018 · 1 comment
Closed

Comments

@xbcratos
Copy link
Contributor

When destroying KinesisProducer instances, destroy method is not shutting down callbackCompletionExecutor. This makes Daemon child object to still be alive occupying 8MB of heap memory each one.

Creating and destroying lots of KinesisProducer instances will result in a Heap Out Of Memory exception.

xbcratos added a commit to xbcratos/amazon-kinesis-producer that referenced this issue Sep 28, 2018
…awslabs#224

When destroying KinesisProducer instances, destroy method is not shutting down callbackCompletionExecutor. This makes Daemon child object to still be alive occupying 8MB of heap memory each one.

Creating and destroying lots of KinesisProducer instances will result in a Heap Out Of Memory exception.
@ankugar
Copy link
Contributor

ankugar commented Dec 8, 2018

The fix was merged with this commit: xbcratos@e153a09.

Thank you for the fix.

@ankugar ankugar closed this as completed Dec 8, 2018
abhilashaseth pushed a commit to abhilashaseth/flink that referenced this issue Oct 9, 2019
abhilashaseth pushed a commit to abhilashaseth/flink that referenced this issue Oct 18, 2019
This fixes
awslabs/amazon-kinesis-producer#224. The issue
has been fixed in Flink 1.10.0 as part of FLINK-12847.
tweise pushed a commit to apache/flink that referenced this issue Oct 24, 2019
This fixes
awslabs/amazon-kinesis-producer#224. The issue
has been fixed in Flink 1.10.0 as part of FLINK-12847.
tweise pushed a commit to apache/flink that referenced this issue Oct 24, 2019
This commit mitigates the issue - awslabs/amazon-kinesis-producer#224

This closes #14175
alphafoobar pushed a commit to alphafoobar/amazon-kinesis-producer that referenced this issue Oct 8, 2020
…awslabs#224

When destroying KinesisProducer instances, destroy method is not shutting down callbackCompletionExecutor. This makes Daemon child object to still be alive occupying 8MB of heap memory each one.

Creating and destroying lots of KinesisProducer instances will result in a Heap Out Of Memory exception.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants