[
https://issues.apache.org/jira/browse/HBASE-9177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13739719#comment-13739719
]
Hadoop QA commented on HBASE-9177:
----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12597897/HBASE-9177.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:red}-1 findbugs{color}. The patch appears to introduce 3 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:red}-1 site{color}. The patch appears to cause mvn site goal to
fail.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.client.TestShell
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/6740//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6740//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6740//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6740//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6740//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6740//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6740//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6740//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6740//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/6740//console
This message is automatically generated.
> Cluster UUID is not properly parsable after rewriting to PB.
> ------------------------------------------------------------
>
> Key: HBASE-9177
> URL: https://issues.apache.org/jira/browse/HBASE-9177
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.98.0, 0.95.2
> Reporter: rajeshbabu
> Assignee: rajeshbabu
> Attachments: HBASE-9177.patch
>
>
> I am facing this problem while testing HBASE-8348(migration).
> ->I have started two clusters with 0.94 version to replicate data from one
> cluster to other. When we have started master,writing cluster id without PB.
> -> killed both the clusters when Replication in progress
> -> running migration script to migrate hdfs and zk data to 0.96.0(No changes
> in cluster id.)
> -> starting 0.96.0 processes.
> Then not able to start region server.
> {code}
> java.io.IOException: Region server startup failed
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.convertThrowableToIOE(HRegionServer.java:2629)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.handleReportForDutyResponse(HRegionServer.java:1202)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.run(HRegionServer.java:802)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: java.lang.NumberFormatException: For input string: " $411f611e
> at
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
> at java.lang.Long.parseLong(Long.java:410)
> at java.lang.Long.valueOf(Long.java:498)
> at java.lang.Long.decode(Long.java:641)
> at java.util.UUID.fromString(UUID.java:208)
> at
> org.apache.hadoop.hbase.zookeeper.ZKClusterId.getUUIDForCluster(ZKClusterId.java:90)
> at
> org.apache.hadoop.hbase.replication.regionserver.Replication.initialize(Replication.java:127)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.newReplicationInstance(HRegionServer.java:2248)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.createNewReplicationInstance(HRegionServer.java:2219)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.setupWALAndReplication(HRegionServer.java:1423)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.handleReportForDutyResponse(HRegionServer.java:1190)
> ... 2 more
> {code}
> {code}
> try {
> clusterId = ClusterId.parseFrom(content);
> } catch (DeserializationException e) {
> throw new IOException("content=" + Bytes.toString(content), e);
> }
> // If not pb'd, make it so.
> if (!ProtobufUtil.isPBMagicPrefix(content)) rewriteAsPb(fs, rootdir,
> idPath, clusterId);
> {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
