hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kihwal Lee (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (HDFS-10347) Namenode report bad block method doesn't log the bad block or datanode.
Date Fri, 29 Apr 2016 20:57:13 GMT

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

Kihwal Lee edited comment on HDFS-10347 at 4/29/16 8:56 PM:
------------------------------------------------------------

+1 straightforward logging change.
I ran {{TestProcessCorruptBlocks}} and saw this in the log.
{noformat}
*DIR* reportBadBlocks for block: BP-1292934650-x.x.x.x-1461963215660:blk_1073741825_1001
 on datanode: 127.0.0.1:41290
{noformat}


was (Author: kihwal):
+1 straightforward logging change.

> 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
>         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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org


Mime
View raw message