Haven't found time, yet. :( Are you bouncing just HBase or Zookeeper as well? I found the ZK client to be frequently the main source delay for "reconnecting". (note also that if run HBase in local mode it will manage ZK for you as well, and the ZK port might change upon restart, which the client does not handle well)
________________________________ From: Kristoffer Sjögren <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Sent: Wednesday, February 12, 2014 11:54 PM Subject: Re: Standard vs Asynchbase client reconnect after HBase restart
@Ted We are using HBase 0.94.6 from CDH 4 to be exact.
@Lars Thanks a lot!
@Mike Just to be clear - the test is using HConnection  and HBaseClient  which is what I refer to as the 'client'. With 'recovered' I mean that the client has gone from 'unresponsive' to being able query and insert data into HBase.
No worries. Let me do some more tests and analyse the communication between zookeeper and HBase to make sure its not a localhost/port screwup from my side.
Ill get back to you. On Thu, Feb 13, 2014 at 11:20 PM, lars hofhansl <[EMAIL PROTECTED]> wrote:
NEW: Monitor These Apps!
Apache Lucene, Apache Solr and all other Apache Software Foundation project and their respective logos are trademarks of the Apache Software Foundation.
Elasticsearch, Kibana, Logstash, and Beats are trademarks of Elasticsearch BV, registered in the U.S. and in other countries. This site and Sematext Group is in no way affiliated with Elasticsearch BV.
Service operated by Sematext