hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "dhruba borthakur (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HDFS-763) DataBlockScanner reporting of bad blocks is slightly misleading
Date Thu, 12 Nov 2009 20:26:39 GMT

     [ https://issues.apache.org/jira/browse/HDFS-763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

dhruba borthakur updated HDFS-763:

    Attachment: scanErrors.txt

Moved the increment of totalScanErrors to follow the check if block was already deleted.

> 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
> 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.

View raw message