Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 86F1D96D6 for ; Mon, 31 Oct 2011 12:20:50 +0000 (UTC) Received: (qmail 64147 invoked by uid 500); 31 Oct 2011 12:20:49 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 64066 invoked by uid 500); 31 Oct 2011 12:20:49 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 64049 invoked by uid 99); 31 Oct 2011 12:20:48 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 31 Oct 2011 12:20:48 +0000 X-ASF-Spam-Status: No, hits=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of ramakrishnas@huawei.com designates 119.145.14.66 as permitted sender) Received: from [119.145.14.66] (HELO szxga03-in.huawei.com) (119.145.14.66) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 31 Oct 2011 12:20:42 +0000 Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LTX002D2JLW8B@szxga03-in.huawei.com> for dev@hbase.apache.org; Mon, 31 Oct 2011 20:20:20 +0800 (CST) Received: from huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LTX00FJ9JLW5R@szxga03-in.huawei.com> for dev@hbase.apache.org; Mon, 31 Oct 2011 20:20:20 +0800 (CST) Received: from BLRNSHTIPL3NC ([10.18.1.33]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LTX00LW0JLUVN@szxml06-in.huawei.com> for dev@hbase.apache.org; Mon, 31 Oct 2011 20:20:20 +0800 (CST) Date: Mon, 31 Oct 2011 17:50:18 +0530 From: Ramkrishna S Vasudevan Subject: RE: Suggest to add a choice of using round-robin assignment on enable-table In-reply-to: To: dev@hbase.apache.org Reply-to: ramakrishnas@huawei.com Message-id: <08BAB27034BB44329AD897ABFDE5DA77@china.huawei.com> Organization: HTIPL MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.4862 X-Mailer: Microsoft Office Outlook 11 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Thread-index: AcySyNRPdDkLsw13TdGvTOHWyqB6mwE/ooCw X-Virus-Checked: Checked by ClamAV on apache.org Hi Yes this will be very useful. Currently we have tweaked our client code so that the region assignment is evenly distributed which may not work always. Regards Ram -----Original Message----- From: Ted Yu [mailto:yuzhihong@gmail.com] Sent: Tuesday, October 25, 2011 9:16 AM To: dev@hbase.apache.org Subject: Re: Suggest to add a choice of using round-robin assignment on enable-table I think it makes sense. Do you mind logging a JIRA ? On Mon, Oct 24, 2011 at 8:15 PM, bijieshan wrote: > Hi, > > Under some scenarios, we use the function of disable/enable HTable. > But currently, enable HTable using the random-assignment. We hope all > the regions show a better distribution, no matter how many regions and > how many regionservers. > > So I suggest to add a choice of using round-robin assignment on > enable-table. > > Does this seem reasonable? > > Thanks, > Jieshan >