hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ken Weiner (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-4235) Attempts to reconnect to expired ZooKeeper sessions
Date Thu, 22 Dec 2011 01:37:30 GMT

    [ https://issues.apache.org/jira/browse/HBASE-4235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13174561#comment-13174561

Ken Weiner commented on HBASE-4235:

I am seeing similar behavior after restart of my HBase 0.90.4 cluster.  The messages that
are printed continuously look like the below. Is it the same issue? Also, ZOOKEEPER-1159 is
not yet resolved yet.  Which upstream issue was marked as invalid?

- Socket connection established to localhost/, initiating session
- Unable to read additional data from server sessionid 0x1345e2d625d0009, likely server has
closed socket, closing socket connection and attempting reconnect
> Attempts to reconnect to expired ZooKeeper sessions
> ---------------------------------------------------
>                 Key: HBASE-4235
>                 URL: https://issues.apache.org/jira/browse/HBASE-4235
>             Project: HBase
>          Issue Type: Task
>    Affects Versions: 0.92.0, 0.90.5
>            Reporter: Andrew Purtell
>            Assignee: Andrew Purtell
> In a couple of instances of short network outages, we have observed afterward zombie
HBase processes attempting over and over to reconnect to expired ZooKeeper sessions. We believe
this is due to ZOOKEEPER-1159. Opening this issue as reference to that.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message