[
https://issues.apache.org/jira/browse/HBASE-9663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13779128#comment-13779128
]
Hadoop QA commented on HBASE-9663:
----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12605287/HBASE-9663-v0.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 hadoop1.0{color}. The patch compiles against the hadoop
1.0 profile.
{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.thrift.TestThriftServer
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/7388//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7388//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7388//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7388//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7388//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7388//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7388//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7388//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7388//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7388//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/7388//console
This message is automatically generated.
> PerformanceEvaluation does not properly honor specified table name parameter
> ----------------------------------------------------------------------------
>
> Key: HBASE-9663
> URL: https://issues.apache.org/jira/browse/HBASE-9663
> Project: HBase
> Issue Type: Bug
> Components: Client, test
> Affects Versions: 0.98.0, 0.96.0
> Reporter: Aleksandr Shulman
> Assignee: Matteo Bertozzi
> Fix For: 0.95.2, 0.96.1
>
> Attachments: HBASE-9663-v0.patch
>
>
> Expected behavior:
> A user should be able to specify a given table for PerformanceEvaluation and
> have that table be used. That table does not need to exist. If it doesn't
> exist, PE will create it.
> Observed behavior:
> In creating the job, PE will use the new table name. However, the map tasks
> will fail because they are still looking for TestTable, which is not there.
> Potential causes:
> In the PE code, we see that the table's is not argument to MR:
> https://github.com/apache/hbase/blob/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/PerformanceEvaluation.java#L723
> Command:
> {code} hbase org.apache.hadoop.hbase.PerformanceEvaluation --table=t2
> sequentialWrite 2{code}
> Output:
> {code}initiating session
> 13/09/26 00:36:02 INFO zookeeper.ClientCnxn: Session establishment complete
> on server <REDACTED>/10.20.187.137:2181, sessionid = 0x14159256f9b0031,
> negotiated timeout = 180000
> 13/09/26 00:36:02 DEBUG client.HConnectionManager$HConnectionImplementation:
> Looked up root region location,
> connection=org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation@c8d427c;
> serverName=<REDACTED>,60020,1380180157520
> 13/09/26 00:36:02 DEBUG client.HConnectionManager$HConnectionImplementation:
> Cached location for .META.,,1.1028785192 is <REDACTED>:60020
> 13/09/26 00:36:02 DEBUG client.ClientScanner: Creating scanner over .META.
> starting at key 't2,,'
> 13/09/26 00:36:02 DEBUG client.ClientScanner: Advancing internal scanner to
> startKey at 't2,,'
> 13/09/26 00:36:02 DEBUG catalog.CatalogTracker: Stopping catalog tracker
> org.apache.hadoop.hbase.catalog.CatalogTracker@466e06d7
> 13/09/26 00:36:02 INFO zookeeper.ZooKeeper: Session: 0x14159256f9b0031 closed
> 13/09/26 00:36:02 INFO zookeeper.ClientCnxn: EventThread shut down
> 13/09/26 00:36:02 INFO zookeeper.ZooKeeper: Initiating client connection,
> connectString=<REDACTED>:2181 sessionTimeout=180000
> watcher=catalogtracker-on-org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation@c8d427c
> 13/09/26 00:36:02 INFO zookeeper.RecoverableZooKeeper: The identifier of this
> process is 10390@<REDACTED>
> 13/09/26 00:36:02 DEBUG catalog.CatalogTracker: Starting catalog tracker
> org.apache.hadoop.hbase.catalog.CatalogTracker@5152cfbb
> 13/09/26 00:36:02 INFO zookeeper.ClientCnxn: Opening socket connection to
> server <REDACTED>/10.20.187.137:2181. Will not attempt to authenticate using
> SASL (unknown error)
> 13/09/26 00:36:02 INFO zookeeper.ClientCnxn: Socket connection established to
> <REDACTED>/10.20.187.137:2181, initiating session
> 13/09/26 00:36:02 INFO zookeeper.ClientCnxn: Session establishment complete
> on server <REDACTED>/10.20.187.137:2181, sessionid = 0x14159256f9b0032,
> negotiated timeout = 180000
> 13/09/26 00:36:02 DEBUG client.ClientScanner: Creating scanner over .META.
> starting at key 't2,,'
> 13/09/26 00:36:02 DEBUG client.ClientScanner: Advancing internal scanner to
> startKey at 't2,,'
> 13/09/26 00:36:02 DEBUG catalog.CatalogTracker: Stopping catalog tracker
> org.apache.hadoop.hbase.catalog.CatalogTracker@5152cfbb
> 13/09/26 00:36:03 INFO zookeeper.ZooKeeper: Session: 0x14159256f9b0032 closed
> 13/09/26 00:36:03 INFO zookeeper.ClientCnxn: EventThread shut down
> 13/09/26 00:36:04 WARN mapred.JobClient: Use GenericOptionsParser for parsing
> the arguments. Applications should implement Tool for the same.
> 13/09/26 00:36:06 INFO input.FileInputFormat: Total input paths to process : 1
> 13/09/26 00:36:06 DEBUG hbase.PerformanceEvaluation: split[0]
> startRow=1363147 rows=104857 totalRows=2097152 clients=2 flushCommits=true
> writeToWAL=true
> 13/09/26 00:36:06 DEBUG hbase.PerformanceEvaluation: split[1]
> startRow=1468004 rows=104857 totalRows=2097152 clients=2 flushCommits=true
> writeToWAL=true
> 13/09/26 00:36:06 DEBUG hbase.PerformanceEvaluation: split[2]
> startRow=1887432 rows=104857 totalRows=2097152 clients=2 flushCommits=true
> writeToWAL=true
> 13/09/26 00:36:06 DEBUG hbase.PerformanceEvaluation: split[3]
> startRow=209714 rows=104857 totalRows=2097152 clients=2 flushCommits=true
> writeToWAL=true
> 13/09/26 00:36:06 DEBUG hbase.PerformanceEvaluation: split[4]
> startRow=524285 rows=104857 totalRows=2097152 clients=2 flushCommits=true
> writeToWAL=true
> 13/09/26 00:36:06 DEBUG hbase.PerformanceEvaluation: split[5]
> startRow=1048576 rows=104857 totalRows=2097152 clients=2 flushCommits=true
> writeToWAL=true
> 13/09/26 00:36:06 DEBUG hbase.PerformanceEvaluation: split[6]
> startRow=1572861 rows=104857 totalRows=2097152 clients=2 flushCommits=true
> writeToWAL=true
> 13/09/26 00:36:06 DEBUG hbase.PerformanceEvaluation: split[7]
> startRow=943713 rows=104857 totalRows=2097152 clients=2 flushCommits=true
> writeToWAL=true
> 13/09/26 00:36:06 DEBUG hbase.PerformanceEvaluation: split[8]
> startRow=314571 rows=104857 totalRows=2097152 clients=2 flushCommits=true
> writeToWAL=true
> 13/09/26 00:36:06 DEBUG hbase.PerformanceEvaluation: split[9]
> startRow=419428 rows=104857 totalRows=2097152 clients=2 flushCommits=true
> writeToWAL=true
> 13/09/26 00:36:06 DEBUG hbase.PerformanceEvaluation: split[10]
> startRow=1258290 rows=104857 totalRows=2097152 clients=2 flushCommits=true
> writeToWAL=true
> 13/09/26 00:36:06 DEBUG hbase.PerformanceEvaluation: split[11]
> startRow=1677718 rows=104857 totalRows=2097152 clients=2 flushCommits=true
> writeToWAL=true
> 13/09/26 00:36:06 DEBUG hbase.PerformanceEvaluation: split[12]
> startRow=1992289 rows=104857 totalRows=2097152 clients=2 flushCommits=true
> writeToWAL=true
> 13/09/26 00:36:06 DEBUG hbase.PerformanceEvaluation: split[13]
> startRow=104857 rows=104857 totalRows=2097152 clients=2 flushCommits=true
> writeToWAL=true
> 13/09/26 00:36:06 DEBUG hbase.PerformanceEvaluation: split[14]
> startRow=629142 rows=104857 totalRows=2097152 clients=2 flushCommits=true
> writeToWAL=true
> 13/09/26 00:36:06 DEBUG hbase.PerformanceEvaluation: split[15] startRow=0
> rows=104857 totalRows=2097152 clients=2 flushCommits=true writeToWAL=true
> 13/09/26 00:36:06 DEBUG hbase.PerformanceEvaluation: split[16]
> startRow=838856 rows=104857 totalRows=2097152 clients=2 flushCommits=true
> writeToWAL=true
> 13/09/26 00:36:06 DEBUG hbase.PerformanceEvaluation: split[17]
> startRow=1782575 rows=104857 totalRows=2097152 clients=2 flushCommits=true
> writeToWAL=true
> 13/09/26 00:36:06 DEBUG hbase.PerformanceEvaluation: split[18]
> startRow=1153433 rows=104857 totalRows=2097152 clients=2 flushCommits=true
> writeToWAL=true
> 13/09/26 00:36:06 DEBUG hbase.PerformanceEvaluation: split[19]
> startRow=733999 rows=104857 totalRows=2097152 clients=2 flushCommits=true
> writeToWAL=true
> 13/09/26 00:36:06 INFO hbase.PerformanceEvaluation: Total # of splits: 20
> 13/09/26 00:36:07 INFO mapred.JobClient: Running job: job_201309260021_0007
> 13/09/26 00:36:08 INFO mapred.JobClient: map 0% reduce 0%
> 13/09/26 00:36:23 INFO mapred.JobClient: Task Id :
> attempt_201309260021_0007_m_000000_0, Status : FAILED
> org.apache.hadoop.hbase.TableNotFoundException: TestTable
> at
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegionInMeta(HConnectionManager.java:1024)
> at
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:889)
> at
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:846)
> at org.apache.hadoop.hbase.client.HTable.finishSetup(HTable.java:271)
> at org.apache.hadoop.hbase.client.HTable.<init>(HTable.java:211)
> at
> org.apache.hadoop.hbase.PerformanceEvaluation$Test.testSetup(PerformanceEvaluation.java:801)
> at
> org.apache.hadoop.hbase.PerformanceEvaluation$Test.test(PerformanceEvaluation.java:820)
> at
> org.apache.hadoop.hbase.PerformanceEvaluation.runOneClient(PerformanceEvaluation.java:1169)
> at
> org.apache.hadoop.hbase.PerformanceEvaluation$EvaluationMapTask.map(PerformanceEvaluation.java:452)
> at org.apache.hadoop.hbase.PerformanceEvaluation$EvaluationMapTask
> {code}
--
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
