Return-Path: Delivered-To: apmail-hadoop-core-commits-archive@www.apache.org Received: (qmail 34106 invoked from network); 4 Apr 2009 18:13:50 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 4 Apr 2009 18:13:50 -0000 Received: (qmail 36274 invoked by uid 500); 4 Apr 2009 18:13:49 -0000 Delivered-To: apmail-hadoop-core-commits-archive@hadoop.apache.org Received: (qmail 36193 invoked by uid 500); 4 Apr 2009 18:13:49 -0000 Mailing-List: contact core-commits-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-dev@hadoop.apache.org Delivered-To: mailing list core-commits@hadoop.apache.org Received: (qmail 36184 invoked by uid 99); 4 Apr 2009 18:13:49 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 04 Apr 2009 18:13:49 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO aurora.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 04 Apr 2009 18:13:47 +0000 Received: from aurora.apache.org (localhost [127.0.0.1]) by aurora.apache.org (8.13.8+Sun/8.13.8) with ESMTP id n34IDRSg012709 for ; Sat, 4 Apr 2009 18:13:27 GMT Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Apache Wiki To: core-commits@hadoop.apache.org Date: Sat, 04 Apr 2009 18:13:27 -0000 Message-ID: <20090404181327.12623.70892@aurora.apache.org> Subject: [Hadoop Wiki] Trivial Update of "Hbase/DesignOverview" by EvgenyRyabitskiy X-Virus-Checked: Checked by ClamAV on apache.org Dear Wiki user, You have subscribed to a wiki page or wiki category on "Hadoop Wiki" for change notification. The following page has been changed by EvgenyRyabitskiy: http://wiki.apache.org/hadoop/Hbase/DesignOverview ------------------------------------------------------------------------------ == Cluster initialization == - + While first start master tries to get root and root region directories from HDFS and after fail creates them and first meta region directory. In next start master will get information about cluster and it's regions. === Assigning regions to HRegionServers === - The first region to be assigned is the ''ROOT region'' which locates all the META regions to be assigned. Each ''META region'' maps a number of user regions which comprise the multiple tables that a particular HBase instance serves. Once all the META regions have been assigned, the master will then assign user regions to the H!RegionServers, attempting to balance the number of regions served by each H!RegionServer. + Each region is assigned to only one H!RegionServer or not assigned yet. The first region to be assigned is the ''ROOT region'' which locates all the META regions to be assigned. Each ''META region'' maps a number of user regions which comprise the multiple tables that a particular HBase instance serves. Once all the META regions have been assigned, the master will then assign user regions to the H!RegionServers, attempting to balance the number of regions served by each H!RegionServer. + + ==== Assigned region ==== + + If region is assigned to some H!RegionServer it means that this region served by this server. While serving region H!RegionServer handles read/write requests to this region, caches last (not yet flushed) modifications in memcache and writes all changes to WAL but persistent reliable storage of regions is provided by HDFS. ==== The META Table ====