[
https://issues.apache.org/jira/browse/ZOOKEEPER-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14113566#comment-14113566
]
chendihao commented on ZOOKEEPER-2022:
--------------------------------------
Here is the log from our server. It's a little misleading if we don't digg for
the negotiatioin timeout.
{quote}
2014-08-25,22:10:48,894 INFO org.apache.zookeeper.ZooKeeper: Initiating client
connection, connectString=10.10.10.22:11000,10.10.10.18:11000,10.10.10.14:11000
sessionTimeout=90000 watcher=hconnection
2014-08-25,22:10:48,898 INFO org.apache.zookeeper.ClientCnxn: Session
establishment complete on server hadoop-server/10.10.10.22:11000, sessionid =
0x2444e61826d6d59, negotiated timeout = 40000
{quote}
> The log of sessionTimeout is inaccurate
> ---------------------------------------
>
> Key: ZOOKEEPER-2022
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2022
> Project: ZooKeeper
> Issue Type: Improvement
> Components: java client
> Reporter: chendihao
> Priority: Minor
>
> When the client constructs ZooKeeper object, it will record the basic info in
> log. But its sessionTimeout may be inaccurate if it's not equal to
> negotiationSessionTimeout. Can we change the description of this info?
> {code:java}
> public ZooKeeper(String connectString, int sessionTimeout, Watcher
> watcher)
> throws IOException
> {
> LOG.info("Initiating client connection, connectString=" +
> connectString
> + " sessionTimeout=" + sessionTimeout + " watcher=" +
> watcher);
> watchManager.defaultWatcher = watcher;
> cnxn = new ClientCnxn(connectString, sessionTimeout, this,
> watchManager);
> cnxn.start();
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
