hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean-Daniel Cryans (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HBASE-3095) Client needs to reconnect if it expires its zk session
Date Thu, 04 Nov 2010 19:40:41 GMT

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

Jean-Daniel Cryans resolved HBASE-3095.
---------------------------------------

      Resolution: Fixed
    Hadoop Flags: [Reviewed]

Committed to trunk the patch I posted on RB plus those comments on top of ZKW.connectionEvent:

{noformat}
* If Disconnected or Expired, this should shutdown the cluster. But, since
* we send a KeeperException.SessionExpiredException along with the abort
* call, it's possible for the Abortable to catch it and try to create a new
* session with ZooKeeper. This is what the client does in HCM.
{noformat}

> Client needs to reconnect if it expires its zk session
> ------------------------------------------------------
>
>                 Key: HBASE-3095
>                 URL: https://issues.apache.org/jira/browse/HBASE-3095
>             Project: HBase
>          Issue Type: Bug
>            Reporter: stack
>            Assignee: Jean-Daniel Cryans
>             Fix For: 0.90.0
>
>
> Clients use an HConnection down in their guts to connect to the hbase cluster.  Master-is-running
and root-region-location are up in zk.   Setup of a new HConnection sets up a connection to
ZooKeeper.  If the session with ZK expires for whatever reason -- in tests they would expire
because zk ensemble was restarted across tests or we might expire because of a long GC, well,
it'll be frustrating to users if we do not just try and resetup the zk connection.

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


Mime
View raw message