Warnings in Zookeeper Server Logs

[Joe Lerner <jo...@gmail.com>]

Hi (yes again):

We have a simple architecture: 2 SOLR Cloud servers (on servers #1 and #2),
and 3 zookeeper instances (on servers #1, #2, and #3). Things appear to work
fine, and I have confirmed that our basic configuration is correct. But we
are seeing TONS of the following warnings in all of our zookeeper server
logs:

2019-01-04 14:48:04,266 [myid:1] - INFO 
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@192] -
Accepted socket connection from /XXX.YY.ZZZ.46:51516
2019-01-04 14:48:04,266 [myid:1] - WARN 
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@368] - caught end
of stream exception
EndOfStreamException: Unable to read additional data from client sessionid
0x0, likely client has closed socket
        at
org.apache.zookeeper.server.NIOServerCnxn.doIO(NIOServerCnxn.java:239)
        at
org.apache.zookeeper.server.NIOServerCnxnFactory.run(NIOServerCnxnFactory.java:203)
        at java.lang.Thread.run(Thread.java:748)
2019-01-04 14:48:04,266 [myid:1] - INFO 
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1044] - Closed
socket connection for client /XXX.YY.ZZZ.46:51516 (no session established
for client)


These messages seem to correspond to similar message we are seeing in the
application client-side logs. (I don’t see any messages that would indicate
Too many connections.) 

Reading the log content, it seems to be saying that a connection is
accepted, but then there is an "end of stream" exception. But our users are
not experiencing any problems--they are searching SOLR like crazy.

Any suggestions?

Thanks!

Joe





--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: Warnings in Zookeeper Server Logs

[Joe Lerner <jo...@gmail.com>]

After a long slog, I am now able to answer my own question, just in case
anybody is listening. 

We determined that when we deploy our application to Tomcat using the Tomcat
deploy service, which happens when we deploy with Jenkins and Ansible, these
errors start. Conversely, if we re-start Tomcat from scratch, the errors go
away. Nothing else we tried (and we tried a lot) worked. Our guess is that
the Zookeeper libraries we build into our application do something that do
not go away, even when the application is re-deployed.

This isn't a great answer from us, as we use Ansible to deploy our
application to production, and we use Jenkins to continuously deploy in
development. But, it is what it is, and at least our logs are readable now.

Joe 



--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html