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

[BUG] - Pulsar Producer leak #136

Closed
david-streamlio opened this issue Jul 6, 2023 · 0 comments · Fixed by #137
Closed

[BUG] - Pulsar Producer leak #136

david-streamlio opened this issue Jul 6, 2023 · 0 comments · Fixed by #137
Labels

Comments

@david-streamlio
Copy link

Describe the bug
When using the connector for a single topic, a customer is seeing the number of connections to the broker increasing dramatically. After reviewing the heap dump, we have determined that the root cause is an excessive number of producer objects are getting created that are never closed.

Expected behavior
Only a single producer for a topic should be created and re-used.

Additional context
The issue was discussed on Slack, with the conclusion being that there is an error in the PulsarWriteTask.scala code that creates a new producer for each task instead of placing it in the cache and reusing it on subsequent calls.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant