[
https://issues.apache.org/jira/browse/HDFS-10347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15264764#comment-15264764
]
Hudson commented on HDFS-10347:
-------------------------------
SUCCESS: Integrated in Hadoop-trunk-Commit #9697 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/9697/])
HDFS-10347. Namenode report bad block method doesn't log the bad block (kihwal:
rev 7da540d03eccc2f97950bf47e8b35ce8c889d1e0)
*
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSNamesystem.java
> Namenode report bad block method doesn't log the bad block or datanode.
> -----------------------------------------------------------------------
>
> Key: HDFS-10347
> URL: https://issues.apache.org/jira/browse/HDFS-10347
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 2.7.0
> Reporter: Rushabh S Shah
> Assignee: Rushabh S Shah
> Priority: Minor
> Fix For: 2.7.3
>
> Attachments: HDFS-10347.patch
>
>
> Currently the method {{FSNamesystem#reportBadBlocks}} doesn't log any
> information regarding the bad block id or the datanode on which corrupt block
> is detected.
> It would be helpful to log that information to debug.
--
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
