[
https://issues.apache.org/jira/browse/HDFS-10625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15397133#comment-15397133
]
Vinayakumar B commented on HDFS-10625:
--------------------------------------
bq. 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.
I see that all current cases of {{sendBlock()}} can print the exception
messages with blockId down the line. So IMO we can avoid multiple redundant
logs about same Exception. Already similar cases are there which would flood
the logs by logging redundant logs in multiple levels. Example, any exception
during the writing, will log at multiple places.
Better we can avoid redundant logging.
> 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: [email protected]
For additional commands, e-mail: [email protected]
