[
https://issues.apache.org/jira/browse/ZOOKEEPER-4791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17810490#comment-17810490
]
Sönke Liebau commented on ZOOKEEPER-4791:
-----------------------------------------
Someone from our team is on the PR, yes. I just opened the issue because he
doesn't have an account here and registration is disabled.
PR should be opened tomorrow I hope.
> Improve logging when the connection to a remote server is closed
> ----------------------------------------------------------------
>
> Key: ZOOKEEPER-4791
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4791
> Project: ZooKeeper
> Issue Type: New Feature
> Components: server
> Affects Versions: 3.9.1
> Reporter: Sönke Liebau
> Priority: Trivial
>
> When a server closes the connection to a remote server, the logging around
> why the connection is being closed could be improved a bit.
> https://github.com/apache/zookeeper/blob/1cc1eb6a2be7323a5c326652d59a070473bb8779/zookeeper-server/src/main/java/org/apache/zookeeper/server/NettyServerCnxn.java#L524
> {code:java}
> ZooKeeperServer zks = this.zkServer;
> if (zks == null || !zks.isRunning()) {
> LOG.info("Closing connection to {} because the
> server is not ready",
> getRemoteSocketAddress());
> close(DisconnectReason.IO_EXCEPTION);
> return;
> }
> {code}
> It would be helpful to log what zkServer is, because it can have multiple
> states that would trigger this shutdown.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
