[
https://issues.apache.org/jira/browse/HDFS-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13112440#comment-13112440
]
Laxman commented on HDFS-2290:
------------------------------
TestProcessCorruptBlocks - Failure seems to be a timing issue.
We are trying to restart the Datanode and expecting the block reporting to
complete in 3 seconds. This may not succeed all the times.
This test is always passing in local dev env. I'm able to recur the failures in
local environment with less sleep time (1 second).
Any suggestion to improve the test-case apart from increasing the sleep time.
> 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
