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 9AB88110E0 for ; Sun, 13 Jul 2014 23:00:37 +0000 (UTC) Received: (qmail 51312 invoked by uid 500); 13 Jul 2014 23:00:33 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 51226 invoked by uid 500); 13 Jul 2014 23:00:32 -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 51212 invoked by uid 99); 13 Jul 2014 23:00:32 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 13 Jul 2014 23:00:32 +0000 X-ASF-Spam-Status: No, hits=0.6 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of yuzhihong@gmail.com designates 209.85.220.53 as permitted sender) Received: from [209.85.220.53] (HELO mail-pa0-f53.google.com) (209.85.220.53) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 13 Jul 2014 23:00:29 +0000 Received: by mail-pa0-f53.google.com with SMTP id kq14so1413102pab.12 for ; Sun, 13 Jul 2014 16:00:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=9KljFXXdENs7DYwbIEIULj0sm3DaJeT4R3kODMkaKUo=; b=ckmMJaX8fCKPAyhTxs7j61/VVvjKSFs6jfiNht4IxETbaaJCKP3ZHC7yZqAzPnsvt2 8cxvLHPeVkaxcjaVelQajpqMiKLNY1/UfxqvpEvPvvX9O2843V4qv36+k89lVXaQyiM1 KNwEHM5y2S2A8OxGXGFdjbCHBM2G9wJ4HIZVyxMGHhx2Cbz4tHzWusR8TrSUwfUDgTCF de1oTTNhoJHJZvVAY4VsMAlRegh9s8MSZsCGyIGtc/yYxMt6BCgRUeVgJ3vvxMkMG/H4 n4yN1drJA3kD1kQidVwS7/wgKcou02983EMneOP0+V+DFyMUtrFPIpvd2UeNoeyRNuSs 2v7A== X-Received: by 10.68.190.98 with SMTP id gp2mr13177057pbc.88.1405292404673; Sun, 13 Jul 2014 16:00:04 -0700 (PDT) Received: from [10.165.191.80] (57.sub-70-197-2.myvzw.com. [70.197.2.57]) by mx.google.com with ESMTPSA id r3sm11900373pdd.8.2014.07.13.16.00.00 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 13 Jul 2014 16:00:00 -0700 (PDT) References: <1405288475243-4061296.post@n3.nabble.com> Mime-Version: 1.0 (1.0) In-Reply-To: <1405288475243-4061296.post@n3.nabble.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: <0474165B-52FF-4CEA-A673-32D66CFE101E@gmail.com> Cc: "user@hbase.apache.org" X-Mailer: iPhone Mail (10B146) From: Ted Yu Subject: Re: Is there an advantage of placing related regions on the same region server/host? Date: Sun, 13 Jul 2014 15:59:59 -0700 To: "user@hbase.apache.org" X-Virus-Checked: Checked by ClamAV on apache.org By related regions, do you mean query would typically involve both regions ?= Cheers On Jul 13, 2014, at 2:54 PM, gomes wrote: > I have few tables, and I have pre partitioned the tables. I would like to > achieve reduced latency. I am just thinking of placing related regions on > the same region server/host. For example, table 1 contains 3 regions > [a,b,c], and table 2 contains 3 regions[x,y,z]. (a,x) contains the data fo= r > some group of users, (b,y) contains the data for some group of users, and > (c,z) and so on.=20 >=20 > If I have two region servers, instead of placing [a,b,c] on one server, an= d > [x,y,z] on other server, is there an advantage of placing related regions > (a,x), (b,y), (c,z) among the region servers? >=20 > Note: I also make sure the regions will not be divided further, or there > will be manual intervention needed to divide the regions further. >=20 >=20 >=20 > -- > View this message in context: http://apache-hbase.679495.n3.nabble.com/Is-= there-an-advantage-of-placing-related-regions-on-the-same-region-server-host= -tp4061296.html > Sent from the HBase User mailing list archive at Nabble.com.