Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: pass (nike.apache.org: domain of stoffe@gmail.com designates
 209.85.192.171 as permitted sender)
MIME-Version: 1.0
Date: Wed, 12 Feb 2014 09:41:50 +0100
Message-ID: 
 <CADSBNAhAjc+0ufeYFpSCUeF8BjJ7R1ySUULRL0=ptj=Qjn8ccA@mail.gmail.com>
Subject: Standard vs Asynchbase client reconnect after HBase restart
From: =?ISO-8859-1?Q?Kristoffer_Sj=F6gren?= <stoffe@gmail.com>
To: user@hbase.apache.org
Content-Type: multipart/alternative; boundary=bcaec521555343612b04f2318b4f

--bcaec521555343612b04f2318b4f
Content-Type: text/plain; charset=ISO-8859-1

Hi

I have some tests that check client behaviour during a controlled HBase
restart. Everything works as expected and the client is able to recover
after a while.

However, after doing the same tests with the Asynchbase I noticed that this
client recovers almost instantly after HBase comes back up - whereas the
standard HConnection recovers much later (around 30 seconds).

I played around with two properties without much time to recovery reduction.

fail.fast.expired.active.master=true
zookeeper.session.timeout=5000

Any tips on how to improve time to recovery?

Cheers,
-Kristoffer

--bcaec521555343612b04f2318b4f--