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 9B4C1F743 for ; Fri, 5 Apr 2013 10:52:17 +0000 (UTC) Received: (qmail 26126 invoked by uid 500); 5 Apr 2013 10:52:17 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 26057 invoked by uid 500); 5 Apr 2013 10:52:16 -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 25856 invoked by uid 99); 5 Apr 2013 10:52:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Apr 2013 10:52:15 +0000 Date: Fri, 5 Apr 2013 10:52:15 +0000 (UTC) From: "ramkrishna.s.vasudevan (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-8279) Performance Evaluation does not consider the table name passed in the argument 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-8279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13623526#comment-13623526 ] ramkrishna.s.vasudevan commented on HBASE-8279: ----------------------------------------------- Ya, you are absolutely right. Every time new PE object is getting created and that is the reason. > Performance Evaluation does not consider the table name passed in the argument > ------------------------------------------------------------------------------ > > Key: HBASE-8279 > URL: https://issues.apache.org/jira/browse/HBASE-8279 > Project: HBase > Issue Type: Bug > Reporter: ramkrishna.s.vasudevan > Assignee: ramkrishna.s.vasudevan > Priority: Minor > Fix For: 0.95.0, 0.98.0, 0.94.7 > > Attachments: HBASE-8279.patch > > > Performance evaluation gives a provision to pass the table name. > The table name is considered when we first initialize the table - like the disabling and creation of tables happens with the name that we pass. > But the write and read test again uses only the default table and so the perf evaluation fails. > I think the problem is like this > {code} > ./hbase org.apache.hadoop.hbase.PerformanceEvaluation --nomapred --table=MyTable2 --presplit=70 randomRead 2 > {code} > {code} > 13/04/04 21:42:07 DEBUG hbase.HRegionInfo: Current INFO from scan results = {NAME => 'MyTable2,00000000000000000002067171,1365126124904.bc9e936f4f8ca8ee55eb90091d4a13b6.', STARTKEY => '00000000000000000002067171', ENDKEY => '', ENCODED => bc9e936f4f8ca8ee55eb90091d4a13b6,} > 13/04/04 21:42:07 INFO hbase.PerformanceEvaluation: Table created with 70 splits > {code} > You can see that the specified table is created with the splits. > But when the read starts > {code} > Caused by: org.apache.hadoop.hbase.exceptions.TableNotFoundException: TestTable > at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegionInMeta(HConnectionManager.java:1157) > at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:1034) > at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:984) > at org.apache.hadoop.hbase.client.HTable.finishSetup(HTable.java:246) > at org.apache.hadoop.hbase.client.HTable.(HTable.java:187) > at org.apache.hadoop.hbase.PerformanceEvaluation$Test.testSetup(PerformanceEvaluation.java:851) > at org.apache.hadoop.hbase.PerformanceEvaluation$Test.test(PerformanceEvaluation.java:869) > at org.apache.hadoop.hbase.PerformanceEvaluation.runOneClient(PerformanceEvaluation.java:1495) > at org.apache.hadoop.hbase.PerformanceEvaluation$1.run(PerformanceEvaluation.java:590) > {code} > It says TestTable not found which is the default table. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira