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 D9E68D1E7 for ; Sat, 3 Nov 2012 15:43:11 +0000 (UTC) Received: (qmail 70384 invoked by uid 500); 3 Nov 2012 15:43:09 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 70313 invoked by uid 500); 3 Nov 2012 15:43:09 -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 70305 invoked by uid 99); 3 Nov 2012 15:43:09 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 03 Nov 2012 15:43:09 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of yuzhihong@gmail.com designates 74.125.82.51 as permitted sender) Received: from [74.125.82.51] (HELO mail-wg0-f51.google.com) (74.125.82.51) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 03 Nov 2012 15:43:03 +0000 Received: by mail-wg0-f51.google.com with SMTP id ed3so2277782wgb.20 for ; Sat, 03 Nov 2012 08:42:42 -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=mTftjKzH4o3RgdUyAgXSMib5zcTfY4QN0DvBrKXTKQA=; b=bLKG3PW3IsvGThXODhCX2LFbYp+D72J6T1jz7w9mPP6b8MK1ygbnzR26F3S75AD8zx Kho8o2Y9KZAZzvGR0WBYgVa2UhyHO8S+fuyqUku1G8oa73hp96FEmpep4Qxy8Qnyq9KU uUemgOVSeRjQcDZyl6KJCbEdBlWXysUCJGKIAcEpDz6m2tugQAwP6TItHtaz7++fUDaA IyFImpkg1AzecaRcw4F+UCuCUxXWL5p3nvOFbWsTX/u/16SAOw+aS+TzjhJxTnnVgLix twVJ9KFcJBWnTtn8IGLPPBvUj2rK8R7qxBNs3AyObWixGMlNur6X0aZWVGEdTwWhHqTT vLSw== MIME-Version: 1.0 Received: by 10.180.100.101 with SMTP id ex5mr6870695wib.16.1351957362705; Sat, 03 Nov 2012 08:42:42 -0700 (PDT) Received: by 10.216.209.152 with HTTP; Sat, 3 Nov 2012 08:42:42 -0700 (PDT) In-Reply-To: References: Date: Sat, 3 Nov 2012 08:42:42 -0700 Message-ID: Subject: Re: HBase scan performance decreases over time. From: Ted Yu To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=f46d0442811a5b067104cd991a14 X-Virus-Checked: Checked by ClamAV on apache.org --f46d0442811a5b067104cd991a14 Content-Type: text/plain; charset=ISO-8859-1 Can you tell us how often you run major compaction after the import ? Have you noticed imbalanced read / write requests in the cluster ? Meaning subset of region servers receive bulk of the writes. We do some manual movement of regions when the above happens. Cheers On Sat, Nov 3, 2012 at 8:12 AM, David Koch wrote: > Hello, > > Every now and then we need to flatten our cluster and re-import all data > from log files (changes in data format, etc.) Afterwards we notice a > significant increase in scan performance. As data is added and shuffled > around between region servers, performance goes down again over time (say a > couple of weeks). Are there any routine operations that one should run > manually, or settings to activate in the HBase configuration to keep the > data well distributed? We use HBase 0.92 as part of a Cloudera4 cluster. > > Thank you, > > /David > --f46d0442811a5b067104cd991a14--