[
https://issues.apache.org/jira/browse/HDFS-10625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15386985#comment-15386985
]
Yiqun Lin commented on HDFS-10625:
----------------------------------
Hi, [~shahrs87], this jira is similar to HDFS-10626. Some codes are both
changed in these two jira. According to the latest comment from [~yzhangal] in
HDFS-10626, I have also changed the code from:
{code}
LOG.warn("Reporting bad {} on {}", block, volume.getBasePath());
{code}
to
{code}
LOG.warn("Reporting bad " + block + " with volume "
+ volume.getBasePath(), e);
{code}
I'm not sure if this line should be also changed in this jira? [~yzhangal], can
take a look for this, and make a coordination.
> 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.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]
