hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wei-Chiu Chuang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-10625) VolumeScanner to report why a block is found bad
Date Thu, 14 Jul 2016 16:29:20 GMT

    [ https://issues.apache.org/jira/browse/HDFS-10625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15377228#comment-15377228
] 

Wei-Chiu Chuang commented on HDFS-10625:
----------------------------------------

looks good to me.
VolumeScanner uses BlockSender and a null stream to verify the integrity of the block. If
the block is corrupt, {{BlockSender#verifyChecksum}} throws a ChecksumException, which details
the location of the corruption.

{code}
throw new ChecksumException("Checksum failed at " + failedPos,
            failedPos);
{code}

>  VolumeScanner to report why a block is found bad
> -------------------------------------------------
>
>                 Key: HDFS-10625
>                 URL: https://issues.apache.org/jira/browse/HDFS-10625
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: datanode, hdfs
>            Reporter: Yongjun Zhang
>            Assignee: Rushabh S Shah
>              Labels: supportability
>         Attachments: HDFS-10625.patch
>
>
> VolumeScanner may report:
> {code}
> WARN org.apache.hadoop.hdfs.server.datanode.VolumeScanner: Reporting bad blk_1170125248_96458336
on /d/dfs/dn
> {code}
> It would be helpful to report the reason why the block is bad, especially when the block
is corrupt, where is the first corrupted chunk in the block.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org


Mime
View raw message