You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After enabling collecting stats (using stats_cb) I've noticed, that some of our services started consuming much more memory. I was not able to trace it back exactly to confluent_kafka library, but disabling stats collection gets rid of the problem.
How to reproduce
I've tried to make a minimal example and came across an unexpected behavior:
In this case, we would see, that _stats_cb has been called ten times, when the flush is called.
My assumption is, that if a service publishes a kafka record relatively infrequently, callbacks build up and can lead to memory issue.
Description
After enabling collecting stats (using
stats_cb
) I've noticed, that some of our services started consuming much more memory. I was not able to trace it back exactly to confluent_kafka library, but disabling stats collection gets rid of the problem.How to reproduce
I've tried to make a minimal example and came across an unexpected behavior:
In this case, we would see, that
_stats_cb
has been called ten times, when theflush
is called.My assumption is, that if a service publishes a kafka record relatively infrequently, callbacks build up and can lead to memory issue.
Is this an intended behaviour?
Checklist
Please provide the following information:
'debug': '..'
as necessary)The text was updated successfully, but these errors were encountered: