You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@zookeeper.apache.org by "Geert Pante (Jira)" <ji...@apache.org> on 2022/06/14 15:56:00 UTC
[jira] [Comment Edited] (ZOOKEEPER-4376) Zookeeper should not warn about "An exception was thrown while closing send thread"
[ https://issues.apache.org/jira/browse/ZOOKEEPER-4376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17554179#comment-17554179 ]
Geert Pante edited comment on ZOOKEEPER-4376 at 6/14/22 3:55 PM:
-----------------------------------------------------------------
This is indeed very annoying. We found it out after upgrading from zookeeper client 3.5 to 3.6. Now we see this error once or twice whenever a client tool ends.
+1 to change it back to DEBUG. In the commit, there was no explanation why it was changed to WARN, and I don't see any valid reasons myself.
In [https://github.com/apache/zookeeper/pull/1889/files] , they changed a similar issue to INFO, but that was server-side, so less relevant.
was (Author: greyfairer):
This is indeed very annoying. We found it out after upgrading from zookeeper client 3.5 to 3.6. Now we see this error once or twice whenever a client tool ends.
+1 to change it back to DEBUG. In the commit, there was no explanation why it was changed to WARN, and I don't see any valid reasons myself.
> Zookeeper should not warn about "An exception was thrown while closing send thread"
> -----------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-4376
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4376
> Project: ZooKeeper
> Issue Type: Bug
> Components: java client
> Affects Versions: 3.6.2
> Reporter: Gaspard Petit
> Priority: Minor
>
> In commit [https://github.com/apache/zookeeper/commit/11c07921c15e2fb7692375327b53f26a583b77ca] the message printed when closing a connection to Zookeeper was changed from being logged as a debug message to a warning message. The comment next to the message confirms that this is "expected" and therefore, it seems unjustified to use a warning level.
> Can we tune this down back to debug (or info) level? I would not mind submitting a pull request if there is consensus.
> The full error we are seeing is the following:
>
> {{An exception was thrown while closing send thread for session 0x1067b8748f00775.}}
>
> with stack strace:
> {{EndOfStreamException: Unable to read additional data from server sessionid 0x1067b8748f00775, likely server has closed socket at org.apache.zookeeper.ClientCnxnSocketNIO.doIO(ClientCnxnSocketNIO.java:77) at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:350) at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1280)}}
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)