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 CAF28988A for ; Thu, 15 Mar 2012 22:13:17 +0000 (UTC) Received: (qmail 20891 invoked by uid 500); 15 Mar 2012 22:13:16 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 20823 invoked by uid 500); 15 Mar 2012 22:13:16 -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 20814 invoked by uid 99); 15 Mar 2012 22:13:16 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Mar 2012 22:13:16 +0000 X-ASF-Spam-Status: No, hits=1.8 required=5.0 tests=HTML_FONT_FACE_BAD,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of hdevml@gmail.com designates 209.85.210.41 as permitted sender) Received: from [209.85.210.41] (HELO mail-pz0-f41.google.com) (209.85.210.41) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Mar 2012 22:13:09 +0000 Received: by dadv6 with SMTP id v6so6663744dad.14 for ; Thu, 15 Mar 2012 15:12:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=2BL8UDjH83kWdKYglxo041wepVekGrIW2vHthwpl4KA=; b=OzQs01q1anAP5PonTSnBDn/IQEIUsYBxXZONCeN29H53Rxoyk8jdMFA5MdtyGoT6UX NC0PE6JH7FhUxdfbwQYKIDKhMNkaFBzcu+tiTP+JMZg1i6VHP81l6pgmctRczgD/2/lQ h/vNbPhUk+uLQ/FGw3UhL9751Takpm6O1YHh1/X7ttp1YreV+R4aK/ZnXE12RTFRim91 s9ixJKR+xathr0uQ/RzRDLSaVU3F/YYExcRgwjoxsjGybiVRD5vBrJRgomACqKSZ9nR7 Py1tReuwfiIxchSRcbD+pLugnmyjs9VO6BKgAWal08Mkc1wapLBLHeblYolTOLIvtopS j3yQ== MIME-Version: 1.0 Received: by 10.68.136.99 with SMTP id pz3mr8149016pbb.114.1331849569310; Thu, 15 Mar 2012 15:12:49 -0700 (PDT) Received: by 10.68.10.136 with HTTP; Thu, 15 Mar 2012 15:12:49 -0700 (PDT) Date: Thu, 15 Mar 2012 15:12:49 -0700 Message-ID: Subject: HBase Region splitting may times. From: hdev ml To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=047d7b10c94379187b04bb4f64f4 X-Virus-Checked: Checked by ClamAV on apache.org --047d7b10c94379187b04bb4f64f4 Content-Type: text/plain; charset=ISO-8859-1 Hi, We are using HBase version 0.90.3 in a 2 node cluster. Maybe this question has been asked too many times. But I could not find a good answer for this. I created a test table with one column family "cf" with 2 columns "a" and "b", each having value of a 3000 character long string. Maximum versions allowed is 3 and maxfilesize is at default 256M. In a loop, I put 100000 rows into it, with 3000 character long values for both a and b. Row key is incremental like row00000000 to row00099999. I applied an outer loop which will run the above 100000 row put loop, 10 times. After running it 10 times, I found that it split into following number of regions for every run. Run Regions 1 4 2 5 3 7 4 10 5 13 6 19 7 19 8 19 9 19 10 19 Question is, why did it stabilize after the 6th run? Shouldn't it stabilize after 3 runs, because number of versions is 3? After 3 runs, It should not split further, because new versions are being added but old version should be purged/deleted. Is that a correct statement? Any help is really appreciated. Thanks, Harshad --047d7b10c94379187b04bb4f64f4--