[
https://issues.apache.org/jira/browse/HBASE-6586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13439835#comment-13439835
]
Hadoop QA commented on HBASE-6586:
----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12542026/hbase-6586-trunk-v4.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 12 new or modified tests.
+1 hadoop2.0. The patch compiles against the hadoop 2.0 profile.
-1 javadoc. The javadoc tool appears to have generated 7 warning messages.
-1 javac. The applied patch generated 5 javac compiler warnings (more than
the trunk's current 4 warnings).
-1 findbugs. The patch appears to introduce 10 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.master.TestAssignmentManager
org.apache.hadoop.hbase.master.TestSplitLogManager
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/2653//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2653//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2653//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2653//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2653//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2653//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/2653//console
This message is automatically generated.
> Quarantine Corrupted HFiles
> ---------------------------
>
> Key: HBASE-6586
> URL: https://issues.apache.org/jira/browse/HBASE-6586
> Project: HBase
> Issue Type: Improvement
> Reporter: Jonathan Hsieh
> Assignee: Jonathan Hsieh
> Attachments: 0001-hbase-6568-hbck-quarantine-v6.patch,
> hbase-6586-92-v3.patch, hbase-6586-94-v3.patch, hbase-6586.patch,
> hbase-6586-trunk-v3.patch, hbase-6586-trunk-v4.patch
>
>
> We've encountered a few upgrades from 0.90 hbases + 20.2/1.x hdfs to 0.92
> hbases + hdfs 2.x that get stuck. I haven't been able to duplicate the
> problem in my dev environment but we suspect this may be related to
> HDFS-3731. On the HBase side, it seems reasonable to quarantine what are
> most likely truncated hfiles, so that can could later be recovered.
> Here's an example of the exception we've encountered:
> {code}
> 2012-07-18 05:55:01,152 ERROR handler.OpenRegionHandler
> (OpenRegionHandler.java:openRegion(346)) - Failed open of
> region=user_mappings,080112102AA76EF98197605D341B9E6C5824D2BC|1001,1317824890618.eaed0e7abc6d27d28ff0e5a9b49c4c
> 0d.
> java.io.IOException: java.lang.IllegalArgumentException: Invalid HFile
> version: 842220600 (expected to be between 1 and 2)
> at
> org.apache.hadoop.hbase.io.hfile.FixedFileTrailer.readFromStream(FixedFileTrailer.java:306)
>
> at org.apache.hadoop.hbase.io.hfile.HFile.pickReaderVersion(HFile.java:371)
> at org.apache.hadoop.hbase.io.hfile.HFile.createReader(HFile.java:387)
> at
> org.apache.hadoop.hbase.regionserver.StoreFile$Reader.<init>(StoreFile.java:1026)
>
> at org.apache.hadoop.hbase.regionserver.StoreFile.open(StoreFile.java:485)
> at
> org.apache.hadoop.hbase.regionserver.StoreFile.createReader(StoreFile.java:566)
>
> at org.apache.hadoop.hbase.regionserver.Store.loadStoreFiles(Store.java:286)
> at org.apache.hadoop.hbase.regionserver.Store.<init>(Store.java:223)
> at
> org.apache.hadoop.hbase.regionserver.HRegion.instantiateHStore(HRegion.java:2534)
>
> at org.apache.hadoop.hbase.regionserver.HRegion.initialize(HRegion.java:454)
> at
> org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:3282)
> at
> org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:3230)
> at
> org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.openRegion(OpenRegionHandler.java:331)
> at
> org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.process(OpenRegionHandler.java:107)
> at org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:169)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>
> at java.lang.Thread.run(Thread.java:619)
> Caused by: java.lang.IllegalArgumentException: Invalid HFile version:
> 842220600 (expected to be between 1 and 2)
> at org.apache.hadoop.hbase.io.hfile.HFile.checkFormatVersion(HFile.java:515)
> at
> org.apache.hadoop.hbase.io.hfile.FixedFileTrailer.readFromStream(FixedFileTrailer.java:303)
>
> ... 17 more
> {code}
> Specifically -- the FixedFileTrailer are incorrect, and seemingly missing.
--
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
