It does not. That last connection, the one in CLOSE_WAIT, is an outbound connection from the broker you are looking at to one of the other brokers. 57821 is the source TCP port, and it is selected (somewhat) randomly from a range of high port numbers. Note that the other end of the connection is 9092, which is the destination port on the remote host.
This is likely one of the replica fetchers. -Todd On Sun, Aug 2, 2015 at 6:58 AM, madhavan kumar <madhavan020...@gmail.com> wrote: > hi all, > i am monitoring the ports that are used by kafka server on my machine. > When i do, > > sudo netstat -ntp | grep 9092 > > it shows, > > tcp 0 0 192.168.122.1:9092 192.168.122.6:59158 > ESTABLISHED 27413/java > tcp 0 0 192.168.122.1:9092 192.168.122.1:58338 > ESTABLISHED 27413/java > *tcp 1 0 192.168.122.1:57821 <http://192.168.122.1:57821> > 192.168.122.1:9092 <http://192.168.122.1:9092> CLOSE_WAIT > 27413/java * > > > The last entry in CLOSE_WAIT state surprises me because > > sudo lsof -i tcp:57821 > shows > > > COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME > java 27413 root 42u IPv4 3266648 0t0 TCP > sk-box:57821->sk-box:9092 (CLOSE_WAIT) > > indicates, that the port 57821 is owned by kafka process > (pid - 27413) > . Does kafka use extra ports other than listening port, 9092 to talk to > itself? > > thanks, > saravana >
