[
https://issues.apache.org/jira/browse/HBASE-8279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13628794#comment-13628794
]
Hadoop QA commented on HBASE-8279:
----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12578179/HBASE-8279_1.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified tests.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop
2.0 profile.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.client.TestFromClientSide
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/5263//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5263//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5263//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5263//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5263//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5263//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5263//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5263//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5263//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/5263//console
This message is automatically generated.
> Performance Evaluation does not consider the args passed in case of more than
> one client
> ----------------------------------------------------------------------------------------
>
> 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.98.0, 0.94.8, 0.95.1
>
> Attachments: HBASE-8279_1.patch, 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.<init>(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
