[
https://issues.apache.org/jira/browse/HDFS-763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12777223#action_12777223
]
Hadoop QA commented on HDFS-763:
--------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12424762/scanErrors.txt
against trunk revision 835534.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
-1 patch. The patch command could not apply the patch.
Console output:
http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h5.grid.sp2.yahoo.net/107/console
This message is automatically generated.
> 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
> Attachments: 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.
