Return-Path: 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 A5C24D871 for ; Thu, 30 Aug 2012 14:36:00 +0000 (UTC) Received: (qmail 56237 invoked by uid 500); 30 Aug 2012 14:35:58 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 56190 invoked by uid 500); 30 Aug 2012 14:35:58 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 56181 invoked by uid 99); 30 Aug 2012 14:35:58 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Aug 2012 14:35:58 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FSL_RCVD_USER,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of mohitanchlia@gmail.com designates 209.85.216.169 as permitted sender) Received: from [209.85.216.169] (HELO mail-qc0-f169.google.com) (209.85.216.169) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Aug 2012 14:35:51 +0000 Received: by qcsd16 with SMTP id d16so1595093qcs.14 for ; Thu, 30 Aug 2012 07:35:30 -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=RRhyArd7FoW8+j0o4MOZ9/J3PuGWPp4/VM4AGxYaYs0=; b=a987nAae7EAw59m/aeioFBxFi7dFx78oN9kf+0JuDgjsIr1L0xsZpJqps5+ugBA53o DdneQflU6LtQfcKt4haXgP8SPrJVX0T+q9Jl8QR023ZnKC8omYBPpNHqH9dPX+4Nq1d7 tnHikGbQJ3McZgBRztFnu9TvCbXmDuJPCKAAz8XWHtGckqpyUJOO4GY5wydRWuK4hdmG 7n6xk0dZlqXZexj8/oS20YJVk4kFZgAYBNfM0Out1v3UuBY+mv3GN+5Zo5nHcn1VvFhK yVJY5lufI+XofM8ghjYmq6fPe6ypOaxVLPtBjs0GmxvYOcyXUzalgRRqtSKLnYFv4lE+ PT6w== MIME-Version: 1.0 Received: by 10.224.179.9 with SMTP id bo9mr11415962qab.86.1346337330002; Thu, 30 Aug 2012 07:35:30 -0700 (PDT) Received: by 10.49.14.232 with HTTP; Thu, 30 Aug 2012 07:35:29 -0700 (PDT) In-Reply-To: References: Date: Thu, 30 Aug 2012 07:35:29 -0700 Message-ID: Subject: Re: md5 hash key and splits From: Mohit Anchlia To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=20cf3030bcc94d7b8c04c87c96ec --20cf3030bcc94d7b8c04c87c96ec Content-Type: text/plain; charset=ISO-8859-1 On Wed, Aug 29, 2012 at 10:50 PM, Stack wrote: > On Wed, Aug 29, 2012 at 9:38 PM, Mohit Anchlia > wrote: > > On Wed, Aug 29, 2012 at 9:19 PM, Stack wrote: > > > >> On Wed, Aug 29, 2012 at 3:56 PM, Mohit Anchlia > > >> wrote: > >> > If I use md5 hash + timestamp rowkey would hbase automatically detect > the > >> > difference in ranges and peforms split? How does split work in such > cases > >> > or is it still advisable to manually split the regions. > >> > > > > What logic would you recommend to split the table into multiple regions > > when using md5 hash? > > > > Its hard to know how well your inserts will spread over the md5 > namespace ahead of time. You could try sampling or just let HBase > take care of the splits for you (Is there a problem w/ your letting > HBase do the splits?) > > From what I;ve read it's advisable to do manual splits since you are able to spread the load in more predictable way. If I am missing something please let me know. > St.Ack > --20cf3030bcc94d7b8c04c87c96ec--