Return-Path: 
 <user-return-49369-apmail-hbase-user-archive=hbase.apache.org@hbase.apache.org>
X-Original-To: apmail-hbase-user-archive@www.apache.org
Delivered-To: apmail-hbase-user-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 9BBB818AF2
	for <apmail-hbase-user-archive@www.apache.org>;
 Mon, 17 Aug 2015 13:59:57 +0000 (UTC)
Received: (qmail 25472 invoked by uid 500); 17 Aug 2015 13:59:51 -0000
Delivered-To: apmail-hbase-user-archive@hbase.apache.org
Received: (qmail 25407 invoked by uid 500); 17 Aug 2015 13:59:51 -0000
Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@hbase.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@hbase.apache.org>
List-Post: <mailto:user@hbase.apache.org>
List-Id: <user.hbase.apache.org>
Reply-To: user@hbase.apache.org
Delivered-To: mailing list user@hbase.apache.org
Received: (qmail 25265 invoked by uid 99); 17 Aug 2015 13:59:50 -0000
Received: from Unknown (HELO spamd1-us-west.apache.org) (209.188.14.142)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Aug 2015 13:59:50 +0000
Received: from localhost (localhost [127.0.0.1])
	by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org)
 with ESMTP id 457B2DE709
	for <user@hbase.apache.org>; Mon, 17 Aug 2015 13:59:50 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org
X-Spam-Flag: NO
X-Spam-Score: 2.9
X-Spam-Level: **
X-Spam-Status: No, score=2.9 tagged_above=-999 required=6.31
	tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,
	HTML_MESSAGE=3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001]
	autolearn=disabled
Authentication-Results: spamd1-us-west.apache.org (amavisd-new);
	dkim=pass (2048-bit key) header.d=gmail.com
Received: from mx1-us-west.apache.org ([10.40.0.8])
	by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new,
 port 10024)
	with ESMTP id uMxjOQFvCWoB for <user@hbase.apache.org>;
	Mon, 17 Aug 2015 13:59:40 +0000 (UTC)
Received: from mail-yk0-f175.google.com (mail-yk0-f175.google.com
 [209.85.160.175])
	by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with
 ESMTPS id 7E9B920757
	for <user@hbase.apache.org>; Mon, 17 Aug 2015 13:59:40 +0000 (UTC)
Received: by ykfw73 with SMTP id w73so73303368ykf.3
        for <user@hbase.apache.org>; Mon, 17 Aug 2015 06:59:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=B7K6ruaCpjre944T2h+rPzKzvAJH/+pt91nsW69dYaw=;
        b=irzybKeDNUejYsO5jBhIHm6mrJyWU6fSNqJcSXRG2kyvwqsZwQn/T2pTjhEDqY+7Ug
         wzmt03UXzkijRJWcriIptTEeMg3476KXP/WHeo0AL5r9MtYgt4XzRk4TW0nfEIgfNZ+F
         SoKJD4XWWicB3+zw211FZaKTDMFB29ENCahNf9WjjVsAJ6WW0fQ0aWysIu9MsVDZB+nD
         V7+pWHlgFHxFbDKZ1+P1nGewtW0P+yve9aQSv76tN0IiOyF+onn9td8ujyxKuyyCjuAl
         bY3CZKXmwjdKDOnnN/DndM1rqecMtl0lNR1Nu/Pq+cjw7o+UMSJRSF0xu/Lv/rkS7453
         Lkww==
MIME-Version: 1.0
X-Received: by 10.170.38.147 with SMTP id 141mr1518317ykg.96.1439819979698;
 Mon, 17 Aug 2015 06:59:39 -0700 (PDT)
Received: by 10.37.208.208 with HTTP; Mon, 17 Aug 2015 06:59:39 -0700 (PDT)
In-Reply-To: 
 <CAFCxkQB85CpaP3emmONkXX9yUhrcARSqQhjrMPjY37XPDc_kaQ@mail.gmail.com>
References: 
 <CAFCxkQB85CpaP3emmONkXX9yUhrcARSqQhjrMPjY37XPDc_kaQ@mail.gmail.com>
Date: Mon, 17 Aug 2015 06:59:39 -0700
Message-ID: 
 <CALte62zrYCSZGxK9uam0mgBmwyfUAMK7PXqo2vb-hcKNV=-h0w@mail.gmail.com>
Subject: Re: hbase doubts
From: Ted Yu <yuzhihong@gmail.com>
To: "user@hbase.apache.org" <user@hbase.apache.org>
Content-Type: multipart/alternative; boundary=001a1137926a6e36cd051d823607

--001a1137926a6e36cd051d823607
Content-Type: text/plain; charset=UTF-8

For #1, take a look at the following in hbase-default.xml :

    <name>hbase.client.keyvalue.maxsize</name>
    <value>10485760</value>

For #2, it would be easier to answer if you can outline access patterns in
your app.

For #3, adjustment according to current region boundaries is done client
side. Take a look at the javadoc for LoadQueueItem
in LoadIncrementalHFiles.java

Cheers

On Mon, Aug 17, 2015 at 6:45 AM, Shushant Arora <shushantarora09@gmail.com>
wrote:

> 1.Is there any max limit on key size of hbase table.
> 2.Is multiple small tables vs one large table which one is preferred.
> 3.for bulk load -when  LoadIncremantalHfile is run it again recalculates
> the region splits based on region boundary - is this division happens on
> client side or server side again at region server or hbase master and then
> it assigns the splits which cross target region boundary to desired
> regionserver.
>

--001a1137926a6e36cd051d823607--