[
https://issues.apache.org/jira/browse/HDFS-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13113161#comment-13113161
]
Laxman commented on HDFS-2290:
------------------------------
{quote}
This is correct since cluster.stopDataNode(0); removes the first node so that
the node at index 1 moves to index 0.
cluster.restartDataNode () adds the new node (previously 0th node) at the end
of the list.
{quote}
Sorry for my misinterpretation. I will correct it.
> 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
> Assignee: Benoy Antony
> Labels: blockmanagement, replication
> Fix For: 0.22.0
>
> Attachments: HDFS-2290_0.22.patch, HDFS-2290_022.patch,
> HDFS-2290_022.patch, HDFS-2290_trunk.patch
>
>
> 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
