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 vivekrishna@gmail.com
 designates 209.85.216.176 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:from:date:message-id:subject:to:content-type;
        b=n/9qvGRaw62ZgAOBwI1OfxDWAquHp4gz1KkLEhub0zycUHPHTqAZmeK/LXRceWLDd5
         xkMLhyuyS3Bmk+u5JSqK1cxJ91KF06Gz4kUcyegKwKOR8KwhhvDBZqfd9bYN33rGPiEv
         ZhgasmnqPFYxVDYnkyXHL822qdW+6+iLdE0iE=
MIME-Version: 1.0
From: Vivek Krishna <vivekrishna@gmail.com>
Date: Tue, 22 Mar 2011 14:46:03 -0400
Message-ID: <AANLkTikL9cFzqo9xdd3o61bDymvRjMrFZrH4DV+zpmDH@mail.gmail.com>
Subject: Manual Region Splitting Question.
To: user@hbase.apache.org
Content-Type: multipart/alternative; boundary=20cf300fb2832c4c0c049f16a987

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

I have GBs of data to be dumped to HBase.  After lots of trials and reading
through the mailing list, I figured out creating regions manually is a good
option because all data was hitting one node initially...

My approach to creating regions is as follow.
    - I sampled like about 1% of the actual data and created say 'n' regions
based on this sample.

Now while doing the insertions, it still hits one node first and then
spreads out.

Our theory is that, the key it encounters while inserting does'nt fall in
the region that we created(using the sample) and hence it inserts as it
would do normally.

So, has anyone approached this problem in a smarter way ?

Viv

--20cf300fb2832c4c0c049f16a987--