Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 65082DE4E for ; Mon, 30 Jul 2012 08:54:37 +0000 (UTC) Received: (qmail 81276 invoked by uid 500); 30 Jul 2012 08:54:36 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 81204 invoked by uid 500); 30 Jul 2012 08:54:36 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 80922 invoked by uid 99); 30 Jul 2012 08:54:35 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Jul 2012 08:54:35 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id 1C1ED1404AF for ; Mon, 30 Jul 2012 08:54:35 +0000 (UTC) Date: Mon, 30 Jul 2012 08:54:35 +0000 (UTC) From: "Hadoop QA (JIRA)" To: issues@hbase.apache.org Message-ID: <2070113232.115605.1343638475118.JavaMail.jiratomcat@issues-vm> In-Reply-To: <1683270434.105268.1343293114609.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Commented] (HBASE-6459) improve speed of create table 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-6459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13424761#comment-13424761 ] Hadoop QA commented on HBASE-6459: ---------------------------------- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12538311/HBASE-6459-trunk-v2.patch against trunk revision . +1 @author. The patch does not contain any @author tags. -1 tests included. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. +1 hadoop2.0. The patch compiles against the hadoop 2.0 profile. +1 javadoc. The javadoc tool did not generate any warning messages. -1 javac. The applied patch generated 5 javac compiler warnings (more than the trunk's current 4 warnings). -1 findbugs. The patch appears to introduce 6 new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed these unit tests: org.apache.hadoop.hbase.coprocessor.TestClassLoading Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/2455//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/2455//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/2455//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/2455//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/2455//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/2455//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/2455//console This message is automatically generated. > improve speed of create table > ----------------------------- > > Key: HBASE-6459 > URL: https://issues.apache.org/jira/browse/HBASE-6459 > Project: HBase > Issue Type: Improvement > Affects Versions: 0.94.0 > Reporter: zhou wenjian > Fix For: 0.96.0 > > Attachments: HBASE-6459-90.patch, HBASE-6459-92.patch, HBASE-6459-94.patch, HBASE-6459-trunk-v2.patch, HBASE-6459-trunk.patch > > > in CreateTableHandler > for (int regionIdx = 0; regionIdx < this.newRegions.length; regionIdx++) { > HRegionInfo newRegion = this.newRegions[regionIdx]; > // 1. Create HRegion > HRegion region = HRegion.createHRegion(newRegion, > this.fileSystemManager.getRootDir(), this.conf, > this.hTableDescriptor, null, false, true); > regionInfos.add(region.getRegionInfo()); > if (regionIdx % batchSize == 0) { > // 2. Insert into META > MetaEditor.addRegionsToMeta(this.catalogTracker, regionInfos); > regionInfos.clear(); > } > // 3. Close the new region to flush to disk. Close log file too. > region.close(); > } > All the region will be create serially. > If we have thousands of regions, that will be a huge cost. > We can improve it by create the region in parallel -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira