zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrey (JIRA)" <j...@apache.org>
Subject [jira] [Created] (ZOOKEEPER-2727) WARN and stacktrace for normally closed socket
Date Fri, 17 Mar 2017 15:48:42 GMT
Andrey created ZOOKEEPER-2727:

             Summary: WARN and stacktrace for normally closed socket
                 Key: ZOOKEEPER-2727
                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2727
             Project: ZooKeeper
          Issue Type: Bug
    Affects Versions: 3.4.9
            Reporter: Andrey

Steps to reproduce:
* setup zookeeper
* setup TCP load balancer. This balancer should check zookeeper clientPort liveness(healthcheck)
by opening and closing TCP connection to clientPort. See https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/
or https://www.digitalocean.com/community/tutorials/how-to-create-your-first-digitalocean-load-balancer#step-2-—-creating-the-load-balancer
for details. 
* in logs:
2017-03-17 15:41:19,843 [myid:1] - WARN  [NIOServerCxn.Factory:]
- 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:228)
	at org.apache.zookeeper.server.NIOServerCnxnFactory.run(NIOServerCnxnFactory.java:203)
	at java.lang.Thread.run(Thread.java:745)

Issue is here:

-1 is a normal socket termination. 

* reduce log level to INFO
* do not log stacktrace.

This message was sent by Atlassian JIRA

View raw message