You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Michi Mutsuzaki (JIRA)" <ji...@apache.org> on 2014/03/25 22:17:15 UTC
[jira] [Resolved] (ZOOKEEPER-1227) Zookeeper logs is showing -1 as
min/max session timeout if there is no sessiontimeout value configured
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michi Mutsuzaki resolved ZOOKEEPER-1227.
----------------------------------------
Resolution: Fixed
ZOOKEEPER-1263 is fixed.
> Zookeeper logs is showing -1 as min/max session timeout if there is no sessiontimeout value configured
> ------------------------------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-1227
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1227
> Project: ZooKeeper
> Issue Type: Sub-task
> Components: server
> Affects Versions: 3.3.3
> Reporter: Rakesh R
> Assignee: Rakesh R
> Priority: Minor
> Fix For: 3.5.0
>
> Attachments: ZOOKEEPER-1227.patch
>
>
> When starting the ZooKeeper without configuring 'minimumSessionTimeOut' and 'maximumSessionTimeOut'.
> I'm seeing the '-1' as the lower and the upper bound, instead it should give the default values : tickTime*2 and tickTime*20
> {noformat}
> 2011-10-14 13:07:18,761 - INFO [main:QuorumPeerConfig@92] - Reading configuration from: /home/amith/CI/source/install/zookeeper/zookeeper1/bin/../conf/zoo.cfg
> 2011-10-14 13:07:19,118 - INFO [main:QuorumPeer@834] - tickTime set to 2000
> 2011-10-14 13:07:19,119 - INFO [main:QuorumPeer@845] - minSessionTimeout set to -1
> 2011-10-14 13:07:19,119 - INFO [main:QuorumPeer@856] - maxSessionTimeout set to -1
> {noformat}
> *Suggestion*
> Move the defaulting logic to the QuorumPeerConfig instead of doing in the QuorumPeer
--
This message was sent by Atlassian JIRA
(v6.2#6252)