Closed satybald closed 7 years ago
Still not clear that the client is a cause but fwiw 0.9.11 removes some allocation overhead.
Thanks, @dehora. We will try this version.
The client's response buffer can be more easily managed in recent versions and there's a different issue open for a byte based consumer, closing for now.
Starting and stopping processor leaves JVM with a bunch of nakadi-java-io un utilized threads, which cause a problem if a large number of subscriptions needs to be consumed if processor exists due to error.
How to simulate:
thead dump exposes a number of nakadi-jave thread being leaked after processor has been stopped.