Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: pass (athena.apache.org: domain of kiran.sarvabhotla@gmail.com
 designates 209.85.212.170 as permitted sender)
MIME-Version: 1.0
Date: Wed, 5 Jun 2013 22:50:37 +0530
Message-ID: 
 <CAMBJfV=X28KecUXVDLNfddwEYAObmF8vmDaToEALZDaYVQu_ew@mail.gmail.com>
Subject: Handling regionserver crashes in production cluster
From: kiran <kiran.sarvabhotla@gmail.com>
To: user@hbase.apache.org
Content-Type: multipart/alternative; boundary=f46d043892478c2c3c04de6b6a59

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

Dear All,

We have production cluster that runs on hbase 0.94.1. The issue we are
facing is whenever one regionserver goes down, the cluster becomes
unresponsive until all the regions are allocated to another
regionserver(s). The transition is taking about 3-5 mins and during this
time we are unable to any do client operation on the cluster.

Is there any way we can make the transition to run in background ?

Also, it is acceptable for us if the client operations such as scan or get
does not work on the rowkeys of regions in transition. But, they are not
working on the entire cluster until all the regions are moved out of
transition. We can't afford 3-5 minutes of downtime.

-- 
Thank you
Kiran Sarvabhotla

-----Even a correct decision is wrong when it is taken late

--f46d043892478c2c3c04de6b6a59--