hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rushabh S Shah (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (HDFS-10625) VolumeScanner to report why a block is found bad
Date Wed, 10 Aug 2016 19:46:20 GMT

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

Rushabh S Shah edited comment on HDFS-10625 at 8/10/16 7:45 PM:
----------------------------------------------------------------

[~vinayrpet]: Can you please review the latest patch (005 version).
I think this should be the last pass.


was (Author: shahrs87):
[~vinayrpet]: Can you please review the latest patch.
I think this should be the last pass.

>  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-1.patch, HDFS-10625.003.patch, HDFS-10625.004.patch,
HDFS-10625.005.patch, 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