You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Patrick Hunt (JIRA)" <ji...@apache.org> on 2009/05/20 00:27:45 UTC
[jira] Updated: (ZOOKEEPER-65) Log information on connection
properties
[ https://issues.apache.org/jira/browse/ZOOKEEPER-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Hunt updated ZOOKEEPER-65:
----------------------------------
Fix Version/s: (was: 3.2.0)
3.3.0
Release Note: not a blocker for 3.2, moving to 3.3
> Log information on connection properties
> ----------------------------------------
>
> Key: ZOOKEEPER-65
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-65
> Project: Zookeeper
> Issue Type: Improvement
> Components: c client, java client, server
> Reporter: Patrick Hunt
> Fix For: 3.3.0
>
>
> We should log information on the connection to enable better field issue debugging.
> In particular if we logged the connection latency (time for req->resp) during session establishment this would give some information about the connection. We should log the initial reading at INFO level, then log subsequent information at trace level.
> Would be nice to log trace events for client/server pings for example.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.