hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tobe <tobeg3oo...@gmail.com>
Subject Re: HBase establishes session with ZooKeeper and close the session immediately
Date Fri, 19 Sep 2014 08:07:44 GMT
I have seen the similar log in someone's blog and it's based on 0.94.20.
The CatalogTracker seems to be initialized for many times.

>
watcher=catalogtracker-on-org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation@69d892a1

On Thu, Sep 18, 2014 at 4:50 PM, tobe <tobeg3oogle@gmail.com> wrote:

>
> I have found that our RegionServers connect to the ZooKeeper frequently.
> They seems to constantly establish the session, close it and reconnect the
> ZooKeeper. Here is the log for both server and client sides. I have no idea
> why this happens and how to deal with it? We're using HBase 0.94.11 and
> ZooKeeper 3.4.4.
>
> The log from HBase RegionServer:
>
> 2014-09-18,16:38:17,867 INFO org.apache.zookeeper.ZooKeeper: Initiating
> client connection, connectString=10.2.201.74:11000,10.2.201.73:11000,
> 10.101.10.67:11000,10.101.10.66:11000,10.2.201.75:11000
> sessionTimeout=30000
> watcher=catalogtracker-on-org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation@69d892a1
> 2014-09-18,16:38:17,868 INFO
> org.apache.zookeeper.client.ZooKeeperSaslClient: Client will use GSSAPI as
> SASL mechanism.
> 2014-09-18,16:38:17,868 INFO org.apache.zookeeper.ClientCnxn: Opening
> socket connection to server lg-hadoop-srv-ct01.bj/10.2.201.73:11000. Will
> attempt to SASL-authenticate using Login Context section 'Client'
> 2014-09-18,16:38:17,868 INFO
> org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper: The identifier of
> this process is 11787@lg-hadoop-srv-st05.bj
> 2014-09-18,16:38:17,868 INFO org.apache.zookeeper.ClientCnxn: Socket
> connection established to lg-hadoop-srv-ct01.bj/10.2.201.73:11000,
> initiating session
> 2014-09-18,16:38:17,870 INFO org.apache.zookeeper.ClientCnxn: Session
> establishment complete on server lg-hadoop-srv-ct01.bj/10.2.201.73:11000,
> sessionid = 0x248782700e52b3c, negotiated timeout = 30000
> 2014-09-18,16:38:17,876 INFO org.apache.zookeeper.ZooKeeper: Session:
> 0x248782700e52b3c closed
> 2014-09-18,16:38:17,876 INFO org.apache.zookeeper.ClientCnxn: EventThread
> shut down
> 2014-09-18,16:38:17,878 INFO
> org.apache.hadoop.hbase.replication.regionserver.ReplicationSink: Total
> replicated: 24
>
> The log from its ZooKeeper server:
>
> 2014-09-18,16:38:17,869 INFO
> org.apache.zookeeper.server.NIOServerCnxnFactory: [myid:2] Accepted socket
> connection from /10.2.201.76:55621
> 2014-09-18,16:38:17,869 INFO org.apache.zookeeper.server.ZooKeeperServer:
> [myid:2] Client attempting to establish new session at /10.2.201.76:55621
> 2014-09-18,16:38:17,870 INFO org.apache.zookeeper.server.ZooKeeperServer:
> [myid:2] Established session 0x248782700e52b3c with negotiated timeout
> 30000 for client /10.2.201.76:55621
> 2014-09-18,16:38:17,872 INFO
> org.apache.zookeeper.server.auth.SaslServerCallbackHandler: [myid:2]
> Successfully authenticated client:
> authenticationID=hbase_srv/hadoop@XIAOMI.HADOOP;
> authorizationID=hbase_srv/hadoop@XIAOMI.HADOOP.
> 2014-09-18,16:38:17,872 INFO
> org.apache.zookeeper.server.auth.SaslServerCallbackHandler: [myid:2]
> Setting authorizedID: hbase_srv
> 2014-09-18,16:38:17,872 INFO org.apache.zookeeper.server.ZooKeeperServer:
> [myid:2] adding SASL authorization for authorizationID: hbase_srv
> 2014-09-18,16:38:17,877 INFO org.apache.zookeeper.server.NIOServerCnxn:
> [myid:2] Closed socket connection for client /10.2.201.76:55621 which had
> sessionid 0x248782700e52b3c
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message