All good ideas -- thank you!
On Fri, Mar 6, 2015 at 2:48 PM, Otis Gospodnetic <otis.gospodne...@gmail.com> wrote: > 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 * Alerting * Anomaly Detection * Centralized Log Management > Solr & Elasticsearch Support * http://sematext.com/ > > > On Fri, Mar 6, 2015 at 4:04 PM, Gwen Shapira <gshap...@cloudera.com> wrote: > >> 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? :) >> >> Similar for consumer, if you use high level consumer and don't close the >> consumer nicely, you may not acknowledge the last messages and they will be >> re-read next time the consumer starts, leading to duplicates. >> >> Gwen >> >> >> >> On Fri, Mar 6, 2015 at 12:40 PM, Stuart Reynolds <s...@stureynolds.com> >> wrote: >> >> > 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? >> > >>
