hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4799) Corrupt replica can be prematurely removed from corruptReplicas map
Date Fri, 10 May 2013 16:45:18 GMT

    [ https://issues.apache.org/jira/browse/HDFS-4799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13654592#comment-13654592

Hudson commented on HDFS-4799:

Integrated in Hadoop-trunk-Commit #3736 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/3736/])
    HDFS-4799. Corrupt replica can be prematurely removed from corruptReplicas map. Contributed
by Todd Lipcon. (Revision 1481084)

     Result = SUCCESS
kihwal : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1481084
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/blockmanagement/BlockManager.java
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/blockmanagement/TestRBWBlockInvalidation.java
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/ha/HATestUtil.java

> Corrupt replica can be prematurely removed from corruptReplicas map
> -------------------------------------------------------------------
>                 Key: HDFS-4799
>                 URL: https://issues.apache.org/jira/browse/HDFS-4799
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 2.0.4-alpha
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Blocker
>             Fix For: 3.0.0, 2.0.5-beta
>         Attachments: hdfs-4799.txt, hdfs-4799.txt, hdfs-4799-unittest.txt
> We saw the following sequence of events in a cluster result in losing the most recent
genstamp of a block:
> - client is writing to a pipeline of 3
> - the pipeline had nodes fail over some period of time, such that it left 3 old-genstamp
replicas on the original three nodes, having recruited 3 new replicas with a later genstamp.
> -- so, we have 6 total replicas in the cluster, three with old genstamps on downed nodes,
and 3 with the latest genstamp
> - cluster reboots, and the nodes with old genstamps blockReport first. The replicas are
correctly added to the corrupt replicas map since they have a too-old genstamp
> - the nodes with the new genstamp block report. When the latest one block reports, chooseExcessReplicates
is called and incorrectly decides to remove the three good replicas, leaving only the old-genstamp

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

View raw message