[
https://issues.apache.org/jira/browse/HDFS-10625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yiqun Lin updated HDFS-10625:
-----------------------------
Attachment: HDFS-10625.003.patch
Thanks a lot for the comment, [~vinayrpet].
{quote}
One problem here, is for the places which expects Specific exception such as
ChecksumException or FileNotFoundException, they get IOException with cause set
as ChecksumException or FNFE.
So its better to not to change in this. Let original IOException thrown back.
Anyway DN logs will be there to catch the replica details.
{quote}
One comment from me for this: Can we print the log replica info when catch the
IOException? So that we can not only see the replica info and also keep the
original IOException.
Other suggestions look good to me. Post a new patch for addressing the latest
comment, thanks for review.
> 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.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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
