Return-Path: Delivered-To: apmail-hadoop-hbase-dev-archive@locus.apache.org Received: (qmail 77995 invoked from network); 13 Feb 2008 00:39:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 13 Feb 2008 00:39:28 -0000 Received: (qmail 48275 invoked by uid 500); 13 Feb 2008 00:39:22 -0000 Delivered-To: apmail-hadoop-hbase-dev-archive@hadoop.apache.org Received: (qmail 48263 invoked by uid 500); 13 Feb 2008 00:39:22 -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 48250 invoked by uid 99); 13 Feb 2008 00:39:22 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Feb 2008 16:39:22 -0800 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.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Feb 2008 00:38:59 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 885C871406C for ; Tue, 12 Feb 2008 16:39:07 -0800 (PST) Message-ID: <7687471.1202863147555.JavaMail.jira@brutus> Date: Tue, 12 Feb 2008 16:39:07 -0800 (PST) From: "Bryan Duxbury (JIRA)" To: hbase-dev@hadoop.apache.org Subject: [jira] Commented: (HBASE-55) [hbase] Improve Master region assignment function MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HBASE-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12568377#action_12568377 ] Bryan Duxbury commented on HBASE-55: ------------------------------------ I think what we actually need to do is better define what "server load" is. After all, we're seeking to make the set of region assignments that will cause all region servers to have the same average load. So to reformulate the name of this issue a little, we need a better way to calculate total server load. I'm thinking this should be a function of the total size of all regions. The rationale behind this is that the bigger the region (ie, the underlying map files), the more time it will take to do gets, puts, compacts, etc. In the long run, machines with bigger regions will be more utilized than systems with smaller regions. So, to balance region assignment, we should sum up all the sizes of all the regions currently assigned per server, calculate an average, and then reduce the load of overloaded servers by deallocating regions from them, and increase the load of underloaded servers by adding newly unassigned regions. To incorporate the daughter regions on different machines concept, we can just add an additional check to skip the same server as was just assigned to. > [hbase] Improve Master region assignment function > ------------------------------------------------- > > Key: HBASE-55 > URL: https://issues.apache.org/jira/browse/HBASE-55 > Project: Hadoop HBase > Issue Type: Improvement > Components: regionserver > Reporter: Bryan Duxbury > Fix For: 0.2.0 > > > We would like the master's region assignment function to take into account more factors when choosing where to assign regions. > > - More advanced accounting of load on regionserver - memory, # requests, etc > - Don't deploy both daughter regions to the same regionserver > - Assign regions where the underlying DFS blocks are hosted if possible > Please add additional ideas in comments as they come up. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.