[
https://issues.apache.org/jira/browse/HDFS-4833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13660006#comment-13660006
]
Todd Lipcon commented on HDFS-4833:
-----------------------------------
It seems like this issue exists in branch-1 as well, best I can tell from code
inspection, but I didn't try reproducing it there.
> Corrupt blocks are not invalidated when first processing repl queues
> --------------------------------------------------------------------
>
> Key: HDFS-4833
> URL: https://issues.apache.org/jira/browse/HDFS-4833
> Project: Hadoop HDFS
> Issue Type: Improvement
> Affects Versions: 2.0.4-alpha
> Reporter: Todd Lipcon
>
> When the NN processes misreplicated blocks in {{processMisReplicatedBlock}}
> (eg during initial startup when first processing repl queues), it does not
> invalidate corrupt replicas unless the block is also over-replicated. This
> can result in replicas stuck in "corrupt" state forever if they were that way
> when the cluster booted.
--
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
