[
https://issues.apache.org/jira/browse/HDFS-2263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13176310#comment-13176310
]
Aaron T. Myers commented on HDFS-2263:
--------------------------------------
Can we not do as Todd suggested? i.e. 'only report "corrupt" if we have a
verifiable case of bad checksum' ? Is there some reason that's impossible to
distinguish from other generic errors?
Though this issue is relatively low priority, I don't think there's any reason
we won't fix the issue, so I'd rather just leave it open.
> Make DFSClient report bad blocks more quickly
> ---------------------------------------------
>
> Key: HDFS-2263
> URL: https://issues.apache.org/jira/browse/HDFS-2263
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: hdfs client
> Affects Versions: 0.20.2
> Reporter: Aaron T. Myers
> Assignee: Harsh J
> Attachments: HDFS-2263.patch
>
>
> In certain circumstances the DFSClient may detect a block as being bad
> without reporting it promptly to the NN.
> If when reading a file a client finds an invalid checksum of a block, it
> immediately reports that bad block to the NN. If when serving up a block a DN
> finds a truncated block, it reports this to the client, but the client merely
> adds that DN to the list of dead nodes and moves on to trying another DN,
> without reporting this to the NN.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
