[
https://issues.apache.org/jira/browse/HADOOP-4810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12657212#action_12657212
]
Hairong Kuang commented on HADOOP-4810:
---------------------------------------
Ant test-patch result:
[exec] -1 overall.
[exec]
[exec] +1 @author. The patch does not contain any @author tags.
[exec]
[exec] +1 tests included. The patch appears to include 3 new or
modified tests.
[exec]
[exec] +1 javadoc. The javadoc tool did not generate any warning
messages.
[exec]
[exec] +1 javac. The applied patch does not increase the total number
of javac compiler warnings.
[exec]
[exec] +1 findbugs. The patch does not introduce any new Findbugs
warnings.
[exec]
[exec] -1 Eclipse classpath. The patch causes the Eclipse classpath to
differ from the contents of the lib directories.
Ant test-core result:
Only org.apache.hadoop.mapred.TestJobTrackerRestart failed.
All failures are known and not related to this patch.
> Data lost at cluster startup time
> ---------------------------------
>
> Key: HADOOP-4810
> URL: https://issues.apache.org/jira/browse/HADOOP-4810
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.18.2
> Reporter: Hairong Kuang
> Assignee: Hairong Kuang
> Priority: Blocker
> Fix For: 0.18.3
>
> Attachments: corruptBlocksStartup.patch,
> corruptBlocksStartup1-br18.patch, corruptBlocksStartup1.patch
>
>
> hadoop dfs -cat file1 returns
> dfs.DFSClient: Could not obtain block blk_XX_0 from any node:
> java.io.IOException: No live nodes contain current block
> Tracing the history of the block from NN log, we found
> WARN org.apache.hadoop.fs.FSNamesystem: Inconsistent size for block
> blk_-6160940519231606858_0 reported from A1.A2.A3.A4:50010 current size is
> 9303872 reported size is 262144
> WARN org.apache.hadoop.fs.FSNamesystem: Deleting block
> blk_-6160940519231606858_0 from A1.A2.A3.A4:50010
> INFO org.apache.hadoop.dfs.StateChange: DIR* NameSystem.invalidateBlock:
> blk_-6160940519231606858_0 on A1.A2.A3.A4:50010
> WARN org.apache.hadoop.fs.FSNamesystem: Error in deleting bad block
> blk_-6160940519231606858_0 org.apache.hadoop.dfs.SafeModeException: Cannot
> invalidate block blk_-6160940519231606858_0. Name node is in safe mode.
> WARN org.apache.hadoop.fs.FSNamesystem: Inconsistent size for block
> blk_-6160940519231606858_0 reported from B1.B2.B3.B4:50010 current size is
> 9303872 reported size is 306688
> WARN org.apache.hadoop.fs.FSNamesystem: Deleting block
> blk_-6160940519231606858_0 from B1.B2.B3.B4:50010
> INFO org.apache.hadoop.dfs.StateChange: DIR* NameSystem.invalidateBlock:
> blk_-6160940519231606858_0 on B1.B2.B3.B4:50010
> WARN org.apache.hadoop.fs.FSNamesystem: Error in deleting bad block
> blk_-6160940519231606858_0 org.apache.hadoop.dfs.SafeModeException: Cannot
> invalidate block blk_-6160940519231606858_0. Name node is in safe mode.
> INFO org.apache.hadoop.dfs.StateChange: BLOCK*
> NameSystem.chooseExcessReplicates: (C1.C2.C3.C4:50010,
> blk_-6160940519231606858_0) is added to recentInvalidateSets
> INFO org.apache.hadoop.dfs.StateChange: BLOCK*
> NameSystem.chooseExcessReplicates: (D1.D2.D3.D4:50010,
> blk_-6160940519231606858_0) is added to recentInvalidateSets
> INFO org.apache.hadoop.dfs.StateChange: BLOCK* ask C1.C2.C3.C4:50010 to
> delete blk_-6160940519231606858_0
> INFO org.apache.hadoop.dfs.StateChange: BLOCK* ask D1.D2.D3.D4:50010 to
> delete blk_-6160940519231606858_0
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
