Discussion:
Zookeeper logging “exception causing close of session 0x0” infinitely in logs
Shantanu Deshmukh
2018-08-06 10:16:37 UTC
Permalink
We have a cluster of 3 kafka+zookeeper. Only on one of our zookeeper
servers we are seeing these logs infinitely getting written in
zookeeper.out log file

WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:***@1033] -
Exception causing close of session 0x0 due to java.io.Exception
INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:***@1033] -
Closed socket connection from /10.189.177.31:65429 (no session
established for client)

I have no idea what this server 10.189.177.31 is. No Kafka consumer is
running on this machine.

No changes to zookeeper was made. Due to disk full issue cluster had
crashed. So we started all brokers and zookeepers. Everything went well
except for this one. What can be done for this case? As zk is logging so
heavily it will fill up the disk again with just these logs. Please help
Manjunath N
2018-08-06 10:58:28 UTC
Permalink
Check this thread. Not sure if it is the same case. you could also enable trace and see if you can find more information.

http://zookeeper-user.578899.n2.nabble.com/chatty-error-Exception-causing-close-of-session-0x0-due-to-java-io-IOException-Len-error-1835955314-td7198695.html <http://zookeeper-user.578899.n2.nabble.com/chatty-error-Exception-causing-close-of-session-0x0-due-to-java-io-IOException-Len-error-1835955314-td7198695.html>

Also, if this host is the zookeeper leader you can restart and observe if the same behavior is reproducible when the leadership moves to another host.
Post by Shantanu Deshmukh
We have a cluster of 3 kafka+zookeeper. Only on one of our zookeeper
servers we are seeing these logs infinitely getting written in
zookeeper.out log file
Exception causing close of session 0x0 due to java.io.Exception
Closed socket connection from /10.189.177.31:65429 (no session
established for client)
I have no idea what this server 10.189.177.31 is. No Kafka consumer is
running on this machine.
No changes to zookeeper was made. Due to disk full issue cluster had
crashed. So we started all brokers and zookeepers. Everything went well
except for this one. What can be done for this case? As zk is logging so
heavily it will fill up the disk again with just these logs. Please help
Loading...