Return-Path: Delivered-To: apmail-hadoop-hbase-user-archive@minotaur.apache.org Received: (qmail 23365 invoked from network); 24 Aug 2009 16:44:24 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 24 Aug 2009 16:44:24 -0000 Received: (qmail 36527 invoked by uid 500); 24 Aug 2009 15:42:47 -0000 Delivered-To: apmail-hadoop-hbase-user-archive@hadoop.apache.org Received: (qmail 36481 invoked by uid 500); 24 Aug 2009 15:42:47 -0000 Mailing-List: contact hbase-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hbase-user@hadoop.apache.org Delivered-To: mailing list hbase-user@hadoop.apache.org Received: (qmail 36470 invoked by uid 99); 24 Aug 2009 15:42:47 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Aug 2009 15:42:47 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of anty.rao@gmail.com designates 209.85.211.177 as permitted sender) Received: from [209.85.211.177] (HELO mail-yw0-f177.google.com) (209.85.211.177) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Aug 2009 15:42:39 +0000 Received: by ywh7 with SMTP id 7so2873161ywh.21 for ; Mon, 24 Aug 2009 08:42:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=Tk+og5GSYAcEVWWbQKSfleUk7QnAD1XFQtfjvcIZ5bM=; b=qhgYv2Dyjbkz+BPyFxorrdpynZ2vuS8FbE2ROWNpZe0ZRO3kmdGTqc8PVeTW34ZCFB FWar2+cpcov7e++iGQlZ1mJHCTYszYkhhdm4kxjb3rSXaKhLFduOaTNJLxuwPoL+ZMq/ SXalzBJBAGPqAA2OrHxZoLWy6gqq4O11qknuU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=WHv1MTxTBq27Qzwan/LeMy13WFhbWBJr5tUT8l2MYJz1y4Ht8VNArkC7R/WlrJhI0H vae4DW4OEGtXf63e+/Xdi6yd9K/W+8+LMCWY41kZGw28jHqFcIzX7UmeJP1u0XUUH7vo qqmOeBwtVQaCT76wIm5vesYiA+HXS7axwoxAs= MIME-Version: 1.0 Received: by 10.101.141.12 with SMTP id t12mr4795991ann.14.1251128538276; Mon, 24 Aug 2009 08:42:18 -0700 (PDT) Date: Mon, 24 Aug 2009 23:42:18 +0800 Message-ID: Subject: how to online the new created region From: Anty To: hbase-user@hadoop.apache.org Content-Type: multipart/alternative; boundary=0016e6d2658917a25d0471e5109d X-Virus-Checked: Checked by ClamAV on apache.org --0016e6d2658917a25d0471e5109d Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit hi: all In the source code of hbase-0.20.0,we can create a table by calling HBaseAdmin.createTable(HTableDescriptor desc) method, In the source code ,that method have completed the fellowing work: 1.create a HRegionInfo for the first region of the table which we want to create. 2.check to see if table already exists. 3.create a region accoriding to the HRegionInfo 4.put a row for the created region into meta table. 5.close the new region to flush it to disk,Close its log file too 6.set the new created region unassigned. Then ,as far as i understand, the regionServer thread call the method hbaseMaster.regionServerReport(....) to communicate with the master, and get instructions from the master.the regionServer thread will process these instructions(massages) , I think the created region above is assigned to a regionServer only after the regionServer processing the massage MSG_REGION_OPEN.but what confusing me most is when processing the massage MSG_REGION_OPEN, it create a region again according to the regionInfo which we have done that in step 3 above ......i can't understand this,maybe i am wrong. Expecting any reply. Thanks in advance! -- Anty Rao --0016e6d2658917a25d0471e5109d--