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 B355510B47 for ; Tue, 3 Sep 2013 10:29:28 +0000 (UTC) Received: (qmail 68582 invoked by uid 500); 3 Sep 2013 10:29:26 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 68258 invoked by uid 500); 3 Sep 2013 10:29:26 -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 68249 invoked by uid 99); 3 Sep 2013 10:29:25 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Sep 2013 10:29:25 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of kiran.sarvabhotla@gmail.com designates 209.85.192.173 as permitted sender) Received: from [209.85.192.173] (HELO mail-pd0-f173.google.com) (209.85.192.173) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Sep 2013 10:29:18 +0000 Received: by mail-pd0-f173.google.com with SMTP id p10so5799959pdj.4 for ; Tue, 03 Sep 2013 03:28:57 -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=v1T8lokTFe/2mwXdNRyFRmWG26TdSDTtVNgTbunbbSc=; b=yjOHfzTUjztIzGQmain172xWAiwez3LkIDV8IaarZM3KBdbRAWh9wnGGGh8kuYb8mG hu5Dy4/gi+06XRt24v66Wxq9yiETkdTrCsirlfMpObUy5C0YQlaWDW9MP9M9OJ0pSjFx xxnTE/QPz0NwtYoi+8dRHUn5D7OwV7/KB9ugUFbETEUv3c86zaxUw0NHnPCtYYs8yhdK /6psRHxW5PBZFUxHEAt0GzH1a/62D/Eyk2BBqBNs3/lCXKkMUi77S5t1lWiwYR83rmto 9W0o6OWIedvdAk7jCEHOzuJGEqlcpshlwCF+IsvnP7o5XiQaQR0Yq97WR9X9hDiWBoKJ 15ZA== MIME-Version: 1.0 X-Received: by 10.68.254.105 with SMTP id ah9mr30575646pbd.87.1378204137695; Tue, 03 Sep 2013 03:28:57 -0700 (PDT) Received: by 10.68.183.99 with HTTP; Tue, 3 Sep 2013 03:28:57 -0700 (PDT) Date: Tue, 3 Sep 2013 15:58:57 +0530 Message-ID: Subject: Performing intra row scans From: kiran To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=047d7b2e10430e2fda04e5782825 X-Virus-Checked: Checked by ClamAV on apache.org --047d7b2e10430e2fda04e5782825 Content-Type: text/plain; charset=ISO-8859-1 Dear All, We have a row where there are a million entries inserted as columns per day. The qualifier structure "prefix-reversetimestamp". I am performing a day wise slice of the columns using Columnrangefilter. When I tried to fetch columns that span within 3 days from the current time. There was no problem at all. When, I tried to increase the number of days to morethan 3, then my entire cluster stops accepting new requests. Is it the case of region hot swapping due to my schema design? Is it a good to have million columns under a single row and growing each day. It is a production cluster, so I can't afford this outage. Please suggest me the workaround to handle this. Hbase version: 0.94.1 My sample code: Scan scan = new Scan(rowBytes, rowBytes); scan.setBatch(200); byte[] startPrefix = prefix + "-" + (Long.Max_value - currentimeroundedtoday); byte[] endPrefix = prefix + "-" + (Long.Max_value - (currenttimeroundedtoday - 7 days)); ColumnRangeFilger crf = new ColumnRangeFilter(startPrefix, true, endPrefix, true); scan.setFilter(crf); -- Thank you Kiran Sarvabhotla -----Even a correct decision is wrong when it is taken late --047d7b2e10430e2fda04e5782825--