BewareMyPower commented on issue #11413:
URL: https://github.com/apache/pulsar/issues/11413#issuecomment-891663001


   The main exception stack was introduced from 
https://github.com/apache/bookkeeper/pull/2587, which added an error level log 
in `shouldRetryOnException`.
   
   ```bash
   $ grep ERROR ~/logs-1.txt
   04:12:47.367 [client-scheduler-OrderedScheduler-0-0] ERROR 
org.apache.bookkeeper.clients.impl.internal.RootRangeClientImplWithRetries - 
Reason for the failure {}
   04:12:48.377 [client-scheduler-OrderedScheduler-1-0] ERROR 
org.apache.bookkeeper.clients.impl.internal.RootRangeClientImplWithRetries - 
Reason for the failure {}
   04:12:49.666 [client-scheduler-OrderedScheduler-0-0] ERROR 
org.apache.bookkeeper.clients.impl.internal.RootRangeClientImplWithRetries - 
Reason for the failure {}
   04:12:50.952 [client-scheduler-OrderedScheduler-1-0] ERROR 
org.apache.bookkeeper.clients.impl.internal.RootRangeClientImplWithRetries - 
Reason for the failure {}
   ```
   
   Other exception stacks are thrown during ZK client's close, like
   
   ```
   04:12:42.868 [main-SendThread(127.0.0.1:2181)] WARN  
org.apache.zookeeper.ClientCnxn - An exception was thrown while closing send 
thread for session 0x1000001599a0005.
     org.apache.zookeeper.ClientCnxn$EndOfStreamException: Unable to read 
additional data from server sessionid 0x1000001599a0005, likely server has 
closed socket
         at 
org.apache.zookeeper.ClientCnxnSocketNIO.doIO(ClientCnxnSocketNIO.java:77) 
~[org.apache.zookeeper-zookeeper-3.6.3.jar:3.6.3]
         at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:350)
 ~[org.apache.zookeeper-zookeeper-3.6.3.jar:3.6.3]
         at 
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1290) 
[org.apache.zookeeper-zookeeper-3.6.3.jar:3.6.3]
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to