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]>
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 [1]
and HBaseClient [2] 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.


On Thu, Feb 13, 2014 at 1:11 AM, Michael Segel <[EMAIL PROTECTED]>wrote:

NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB