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 A251411D71 for ; Fri, 27 Jun 2014 19:58:00 +0000 (UTC) Received: (qmail 14265 invoked by uid 500); 27 Jun 2014 19:57:58 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 14192 invoked by uid 500); 27 Jun 2014 19:57: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 14173 invoked by uid 99); 27 Jun 2014 19:57:58 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Jun 2014 19:57:58 +0000 X-ASF-Spam-Status: No, hits=2.8 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of yuzhihong@gmail.com designates 209.85.213.42 as permitted sender) Received: from [209.85.213.42] (HELO mail-yh0-f42.google.com) (209.85.213.42) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Jun 2014 19:57:53 +0000 Received: by mail-yh0-f42.google.com with SMTP id i57so3416911yha.29 for ; Fri, 27 Jun 2014 12:57:33 -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=tJ2bxIIrA0OsXhS7GrG6ZoYhqueZj9s+SiTk1oYV9u4=; b=pH/JSKmEauZB+2zMyqPwh/yhEsLcWqTYwNnNr7qBmO1f0ABqS78GGZi5aRy8/BJbVW tTrFcch7J2OW/B0jNJSdbEnURe/7xhfJxnv54W2obRkmB18yaEDriZeVys/wPIHqeKev Oz3spTRMgBj8eyskdMe7C9+YUKzcrYZg6x++Lb3ajP6MWLOTS33AqTbFiGhdqhClXEsV mlzJWH2J02fed2CmfeIR+QlUqJVtyeyH1XY+mJqxUkXvc2uyQTX40jsXteiYK0Em/DN6 qRQD5YkCS32o+AzGuwCxgMYsZze7FgirJKgVwI3drN1zpeM9xDqjwCT7ZLUEl7/AGOir pLYw== MIME-Version: 1.0 X-Received: by 10.236.8.103 with SMTP id 67mr35033821yhq.29.1403899053124; Fri, 27 Jun 2014 12:57:33 -0700 (PDT) Received: by 10.170.55.137 with HTTP; Fri, 27 Jun 2014 12:57:33 -0700 (PDT) In-Reply-To: <1403898734355-4060823.post@n3.nabble.com> References: <1403898734355-4060823.post@n3.nabble.com> Date: Fri, 27 Jun 2014 12:57:33 -0700 Message-ID: Subject: Re: HBase Disabled Table Resource Consumption? From: Ted Yu To: "user@hbase.apache.org" Content-Type: multipart/alternative; boundary=089e01633c625cb29404fcd6b8e1 X-Virus-Checked: Checked by ClamAV on apache.org --089e01633c625cb29404fcd6b8e1 Content-Type: text/plain; charset=UTF-8 bq. Will it affect hbase region server block cache No. bq. adding up may go beyond 200 per region server? I don't think this is a problem. Cheers On Fri, Jun 27, 2014 at 12:52 PM, Parkirat wrote: > Hi, > > I have a table with many regions and huge data, which I have disabled, as I > may not need it anymore. > > Could anybody tell me, how would such a table(lying idle) will affect my > cluster resources? Assuming I dont have any problems with hard disk or dfs > space and namenode block counts. > > Will it affect hbase region server block cache or hbase write/read > performance in any way? > > Or will it affect if regions from other tables increase over time and > regions from this disabled table adding up may go beyond 200 per region > server? > > Regards, > Parkirat Singh Bagga. > > > > -- > View this message in context: > http://apache-hbase.679495.n3.nabble.com/HBase-Disabled-Table-Resource-Consumption-tp4060823.html > Sent from the HBase User mailing list archive at Nabble.com. > --089e01633c625cb29404fcd6b8e1--