[
https://issues.apache.org/jira/browse/HDFS-763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779565#action_12779565
]
Hudson commented on HDFS-763:
-----------------------------
Integrated in Hdfs-Patch-h5.grid.sp2.yahoo.net #118 (See
[http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h5.grid.sp2.yahoo.net/118/])
. Fix slightly misleading report from DataBlockScanner
about corrupted scans. (dhruba)
> DataBlockScanner reporting of bad blocks is slightly misleading
> ---------------------------------------------------------------
>
> Key: HDFS-763
> URL: https://issues.apache.org/jira/browse/HDFS-763
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: data-node
> Affects Versions: 0.20.1
> Reporter: dhruba borthakur
> Assignee: dhruba borthakur
> Fix For: 0.22.0
>
> Attachments: scanErrors.txt, scanErrors.txt, scanErrors.txt
>
>
> The Datanode generates a report of the period block scanning that verifies
> crcs. It reports something like the following:
> Scans since restart : 192266
> Scan errors since restart : 33
> Transient scan errors : 0
> The statement saying that there were 33 errors is slightly midleading because
> these are not crc mismatches, rather the block was being deleted when the crc
> verification was about to happen.
> I propose that DataBlockScanner.totalScanErrors is not updated if the
> dataset.getFile(block) is null, i.e. the block is now deleted from the
> datanode.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
