Description
We have faced the problem that some kafka network threads may fail, so that jstack attached to Kafka process showed fewer threads than we had defined in our Kafka configuration. This leads to API requests processed by this thread getting stuck unresponed.
There were no error messages in the log regarding thread failure.
We have examined Kafka code to find out there is no top try-catch block in the network thread code, which could at least log possible errors.
Could you add top-level try-catch block for the network thread, which should recover network thread in case of exception?
Attachments
Issue Links
- duplicates
-
KAFKA-2595 Processor thread dies due to an uncaught NoSuchElementException
- Resolved