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 DAB1817816 for ; Tue, 17 Mar 2015 14:27:53 +0000 (UTC) Received: (qmail 58921 invoked by uid 500); 17 Mar 2015 14:27:47 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 58846 invoked by uid 500); 17 Mar 2015 14:27:47 -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 58835 invoked by uid 99); 17 Mar 2015 14:27:46 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Mar 2015 14:27:46 +0000 X-ASF-Spam-Status: No, hits=3.2 required=5.0 tests=HTML_MESSAGE,SPF_SOFTFAIL X-Spam-Check-By: apache.org Received-SPF: softfail (athena.apache.org: transitioning domain of ted@mentacapital.com does not designate 65.243.166.50 as permitted sender) Received: from [65.243.166.50] (HELO S2K8MNTAEXC3.mentacapital.local) (65.243.166.50) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Mar 2015 14:27:41 +0000 Received: from S2K8MNTAEXC3.mentacapital.local ([fe80::3c25:e2cb:93b7:9d49]) by S2K8MNTAEXC3.mentacapital.local ([fe80::4d25:fc5f:3391:4f0b%10]) with mapi; Tue, 17 Mar 2015 07:26:59 -0700 From: Ted Tuttle To: hbase-user CC: Development Subject: introducing nodes w/ more storage Thread-Topic: introducing nodes w/ more storage Thread-Index: AdBgvmx5XamDTq+mTMir4uD5DgIfkA== Date: Tue, 17 Mar 2015 14:26:57 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-Type: multipart/alternative; boundary="_000_D54786A40049124EA5EFE0486D800FFA88DE90D9S2K8MNTAEXC3men_" MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org --_000_D54786A40049124EA5EFE0486D800FFA88DE90D9S2K8MNTAEXC3men_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello- Sometime back I asked a question about introducing new nodes w/ more storag= e that existing nodes. I was told at the time that HBase will not be able = to utilize the additional storage; I assumed at the time that regions are a= llocated to nodes in something like a round-robin fashion and the node with= the least storage sets the limit for how much each node can utilize. My question this time around has to do with nodes w/ unequal numbers of vol= umes: Does HBase allocate regions based on nodes or volumes on the nodes? = I am hoping I can add a node with 8 volumes totaling 8X TB and all the volu= mes will be filled. This even though legacy nodes have 5 volumes and total= storage of 5X TB. Fact or fantasy? Thanks, Ted --_000_D54786A40049124EA5EFE0486D800FFA88DE90D9S2K8MNTAEXC3men_--