hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-2290) Block with corrupt replica is not getting replicated
Date Fri, 26 Aug 2011 16:44:29 GMT

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

Todd Lipcon commented on HDFS-2290:
-----------------------------------

Hasn't this always been the case, that if there's a machine with a corrupt replica, it shouldn't
be a target for the new replica? That is to say, the DN can't accept a new replica of the
same block before it has deleted the old one?

If you start a 4th DN in the cluster, does replication proceed?

> Block with corrupt replica is not getting replicated
> ----------------------------------------------------
>
>                 Key: HDFS-2290
>                 URL: https://issues.apache.org/jira/browse/HDFS-2290
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: name-node
>    Affects Versions: 0.22.0
>            Reporter: Konstantin Shvachko
>             Fix For: 0.22.0
>
>
> A block has one replica marked as corrupt and two good ones. countNodes() correctly detects
that there are only 2 live replicas, and fsck reports the block as under-replicated. But ReplicationMonitor
never schedules replication of good replicas.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message