hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HBASE-1998) Check that session timeout is actually being set; it doesn't seem to be
Date Tue, 07 Dec 2010 21:39:08 GMT

     [ https://issues.apache.org/jira/browse/HBASE-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

stack resolved HBASE-1998.

    Resolution: Fixed

Fixed by zk 3.3.2:

2010-12-07 18:57:32,025 INFO org.apache.zookeeper.ZooKeeper: Initiating client connection,
connectString=sv2borg180:20001 sessionTimeout=180000 watcher=master:60000
2010-12-07 18:57:32,046 INFO org.apache.zookeeper.ClientCnxn: Opening socket connection to
server sv2borg180/
2010-12-07 18:57:32,051 INFO org.apache.zookeeper.ClientCnxn: Socket connection established
to sv2borg180/, initiating session
2010-12-07 18:57:32,121 INFO org.apache.zookeeper.ClientCnxn: Session establishment complete
on server sv2borg180/, sessionid = 0x12cc23218570000, negotiated timeout
= 180000

> Check that session timeout is actually being set; it doesn't seem to be
> -----------------------------------------------------------------------
>                 Key: HBASE-1998
>                 URL: https://issues.apache.org/jira/browse/HBASE-1998
>             Project: HBase
>          Issue Type: Bug
>            Reporter: stack
> The just-previous issue is about relation of tick time to session timeout.  We need to
fix that.  Independent, it would seem that session timeouts are after 30 seconds, not the
40 seconds we'd expect passing in a tick time of 2 seconds and a default sessino timout of
60 seconds.  Check.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message