Return-Path: Delivered-To: apmail-hadoop-hbase-dev-archive@minotaur.apache.org Received: (qmail 80662 invoked from network); 19 Feb 2010 20:06:50 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 19 Feb 2010 20:06:50 -0000 Received: (qmail 20650 invoked by uid 500); 19 Feb 2010 20:06:49 -0000 Delivered-To: apmail-hadoop-hbase-dev-archive@hadoop.apache.org Received: (qmail 20623 invoked by uid 500); 19 Feb 2010 20:06:49 -0000 Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hbase-dev@hadoop.apache.org Delivered-To: mailing list hbase-dev@hadoop.apache.org Received: (qmail 20613 invoked by uid 99); 19 Feb 2010 20:06:49 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Feb 2010 20:06:49 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Feb 2010 20:06:48 +0000 Received: from brutus.apache.org (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id BEA6629A002F for ; Fri, 19 Feb 2010 12:06:28 -0800 (PST) Message-ID: <651933342.397621266609988779.JavaMail.jira@brutus.apache.org> Date: Fri, 19 Feb 2010 20:06:28 +0000 (UTC) From: "stack (JIRA)" To: hbase-dev@hadoop.apache.org Subject: [jira] Resolved: (HBASE-2241) Change balancer sloppyness from 0.1 to 0.3 In-Reply-To: <371960819.397131266609267928.JavaMail.jira@brutus.apache.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-2241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-2241. -------------------------- Resolution: Fixed Assignee: stack Committed branch and trunk. > Change balancer sloppyness from 0.1 to 0.3 > ------------------------------------------ > > Key: HBASE-2241 > URL: https://issues.apache.org/jira/browse/HBASE-2241 > Project: Hadoop HBase > Issue Type: Bug > Reporter: stack > Assignee: stack > Fix For: 0.20.4, 0.21.0 > > Attachments: 2241.patch > > > This is a quick workaround until we do a better balancer. > Taking a region off line when cluster is under load is bad news. Latency goes up as we wait on regions to come up in new locations. > The load balancer should only cut in if the cluster is way out of alignment. > I'd argue that 10% deviance from the avg. is not good enough reason moving regions around when cluster is under load. > Balancer already has a knack for cutting in at most inopportune moments: during cluster startup, when new node is added to a small cluster, or moving a region just after its been opened on a node. We'll need to do a better balancer but meantime lets just allow that region loading can be sloppier, say 20% or 30% off the average before balancer cuts in. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.