[
https://issues.apache.org/jira/browse/ZOOKEEPER-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14113574#comment-14113574
]
chendihao commented on ZOOKEEPER-2022:
--------------------------------------
Thanks [~rakeshr]. I prefer to add more message in the first log, which reminds
me to find out the real negotiation timeout.
For most beginners like me, they may not know about the process of converting
sessionTimeout to negotiationTimeout.
> 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)
