[
https://issues.apache.org/jira/browse/HBASE-5599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13249767#comment-13249767
]
Hadoop QA commented on HBASE-5599:
----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12521930/hbase-5599-trunk_v7.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 6 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any 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.regionserver.wal.TestLogRolling
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/1453//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/1453//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/1453//console
This message is automatically generated.
> The hbck tool can not fix the six scenarios, it is NO_VERSION_FILE,
> NOT_IN_META_OR_DEPLOYED, NOT_IN_META, SHOULD_NOT_BE_DEPLOYED,
> FIRST_REGION_STARTKEY_NOT_EMPTY, HOLE_IN_REGION_CHAIN.
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-5599
> URL: https://issues.apache.org/jira/browse/HBASE-5599
> Project: HBase
> Issue Type: New Feature
> Components: hbck
> Affects Versions: 0.90.6
> Reporter: fulin wang
> Assignee: fulin wang
> Fix For: 0.90.6
>
> Attachments: 0.90-surefire-report-hbck.html, hbase-5599-0.90.patch,
> hbase-5599-0.90_v2.patch, hbase-5599-0.90_v3.patch, hbase-5599-0.90_v5.patch,
> hbase-5599-0.90_v6.patch, hbase-5599-0.90_v7.patch, hbase-5599-0.92_v5.patch,
> hbase-5599-0.94_v5.patch, hbase-5599-trunk_v5.patch, hbase-5599-trunk_v7.patch
>
>
> The hbck tool can not fix the six scenarios.
> 1. Version file does not exist in root dir.
> Fix: I try to create a version file by 'FSUtils.setVersion' method.
>
> 2. [REGIONNAME][KEY] on HDFS, but not listed in META or deployed on any
> region server.
> Fix: I get region info form the hdfs file, this region info write to
> '.META.' table.
>
> 3. [REGIONNAME][KEY] not in META, but deployed on [SERVERNAME]
> Fix: I get region info form the hdfs file, this region info write to
> '.META.' table.
>
> 4. [REGIONNAME] should not be deployed according to META, but is deployed on
> [SERVERNAME]
> Fix: Close this region.
>
> 5. First region should start with an empty key. You need to create a new
> region and regioninfo in HDFS to plug the hole.
> Fix: The region info is not in hdfs and .META., so it create a empty
> region for this error.
> 6. There is a hole in the region chain between [KEY] and [KEY]. You need to
> create a new regioninfo and region dir in hdfs to plug the hole.
> Fix: The region info is not in hdfs and .META., so it create a empty region
> for this hole.
>
--
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
