Hi,
I think you can look at open file descriptors (network connections use
FDs). For example:
https://apps.sematext.com/spm-reports/s/IoQDvdT0Ig -- all good
https://apps.sematext.com/spm-reports/s/v5Hvwta7PP -- Otis restarting 2
consumers
lsof probably shows it, too.
Otis
--
Monitoring *
One of our staff has has been terrible at adding finally clauses to
close kafka resources.
Does the kafka scala/Java client maintain a count or list of open
producers/consumers/client connections?
It doesn't keep track specifically, but there are open sockets that may
take a while to clean themselves up.
Note that if you use the async producer and don't close the producer
nicely, you may miss messages as the connection will close before all
messages are sent. Guess how we found out? :)
You could also take a thread dump to try to find them by their network
threads. For example this is how new producer network threads are named:
String ioThreadName = kafka-producer-network-thread +
(clientId.length() 0 ? | + clientId : );
On Fri, Mar 6, 2015 at 1:04 PM, Gwen Shapira
