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 BFC3F10725 for ; Mon, 22 Jul 2013 23:22:41 +0000 (UTC) Received: (qmail 56552 invoked by uid 500); 22 Jul 2013 23:22:41 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 56419 invoked by uid 500); 22 Jul 2013 23:22:41 -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 56411 invoked by uid 99); 22 Jul 2013 23:22:41 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Jul 2013 23:22:41 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of vrodionov@carrieriq.com designates 204.235.122.16 as permitted sender) Received: from [204.235.122.16] (HELO obmail.carrieriq.com) (204.235.122.16) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Jul 2013 23:22:34 +0000 From: Vladimir Rodionov To: "dev@hbase.apache.org" , lars hofhansl Date: Mon, 22 Jul 2013 16:21:53 -0700 Subject: RE: Smarter Region assignment policy? Thread-Topic: Smarter Region assignment policy? Thread-Index: Ac6HL+hSptbj1Oy8Tuu0F0Fd1kFJNgAAlhWZ Message-ID: References: , <1374519356.75862.YahooMailNeo@web140601.mail.bf1.yahoo.com>,<1374520419.15227.YahooMailNeo@web140604.mail.bf1.yahoo.com> ,<1374534271.17836.YahooMailNeo@web140604.mail.bf1.yahoo.com> In-Reply-To: <1374534271.17836.YahooMailNeo@web140604.mail.bf1.yahoo.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US x-kse-antivirus-interceptor-info: fallback Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org Is not this https://issues.apache.org/jira/browse/HBASE-6143? Best regards, Vladimir Rodionov Principal Platform Engineer Carrier IQ, www.carrieriq.com e-mail: vrodionov@carrieriq.com ________________________________________ From: lars hofhansl [larsh@apache.org] Sent: Monday, July 22, 2013 4:04 PM To: dev@hbase.apache.org Subject: Re: Smarter Region assignment policy? Hmm... So that's an interesting bug then. Might filing a jira? -- Lars ----- Original Message ----- From: Vladimir Rodionov To: "dev@hbase.apache.org" ; lars hofhansl Cc: Sent: Monday, July 22, 2013 3:30 PM Subject: RE: Smarter Region assignment policy? OK, you right and I was not. If I do not disable/enables tables after clust= er restart all regions seem get assigned correctly. I think its disabling/enabling tables shuffles regions in a bad way. Best regards, Vladimir Rodionov Principal Platform Engineer Carrier IQ, www.carrieriq.com e-mail: vrodionov@carrieriq.com ________________________________________ From: lars hofhansl [larsh@apache.org] Sent: Monday, July 22, 2013 12:13 PM To: dev@hbase.apache.org; lars hofhansl Subject: Re: Smarter Region assignment policy? This is the one: https://issues.apache.org/jira/browse/HBASE-4402 I assume you let the master wait sufficiently to give all RegionServer a ch= ance to sign in? -- Lars ________________________________ From: lars hofhansl To: "dev@hbase.apache.org" Sent: Monday, July 22, 2013 11:55 AM Subject: Re: Smarter Region assignment policy? I faintly remember there was a jira that attempted to assign the regions to= the same region servers after a restart based on existing .META. informati= on (if possible). Will try to find that and see why it is not working as expected. -- Lars ________________________________ From: Vladimir Rodionov To: "dev@hbase.apache.org" Sent: Monday, July 22, 2013 11:43 AM Subject: RE: Smarter Region assignment policy? Yes, its related but not what I am looking for. Locality index is approaching to 100% after major compaction of all tables.= Its often > 90% during regular operation of a cluster, but is far below 50% when cluster restarts. Can assignment manager take int= o account previous region assignments on node/cluster start up? That is what I am looking for. How hard is to implem= ent this feature? Best regards, Vladimir Rodionov Principal Platform Engineer Carrier IQ, www.carrieriq.com e-mail: vrodionov@carrieriq.com ________________________________________ From: Ted Yu [yuzhihong@gmail.com] Sent: Monday, July 22, 2013 11:06 AM To: dev@hbase.apache.org Subject: Re: Smarter Region assignment policy? Please take a look at https://issues.apache.org/jira/browse/HBASE-4755 On Mon, Jul 22, 2013 at 10:56 AM, Vladimir Rodionov wrote: > It seems that current (0.94.6) region assignment on start up policy is no= t > that smart and does not utilize hdfs block locality > Are there any open HBase JIRA ticket(s) that addresses the issue? > > Best regards, > Vladimir Rodionov > Principal Platform Engineer > Carrier IQ, www.carrieriq.com > e-mail: vrodionov@carrieriq.com > > > Confidentiality Notice: The information contained in this message, > including any attachments hereto, may be confidential and is intended to = be > read only by the individual or entity to whom this message is addressed. = If > the reader of this message is not the intended recipient or an agent or > designee of the intended recipient, please note that any review, use, > disclosure or distribution of this message or its attachments, in any for= m, > is strictly prohibited. If you have received this message in error, plea= se > immediately notify the sender and/or Notifications@carrieriq.com and > delete or destroy any copy of this message and its attachments. > Confidentiality Notice: The information contained in this message, includi= ng any attachments hereto, may be confidential and is intended to be read o= nly by the individual or entity to whom this message is addressed. If the r= eader of this message is not the intended recipient or an agent or designee= of the intended recipient, please note that any review, use, disclosure or= distribution of this message or its attachments, in any form, is strictly = prohibited. If you have received this message in error, please immediately= notify the sender and/or Notifications@carrieriq.com and delete or destroy= any copy of this message and its attachments.