hadoop-hdfs-issues mailing list archives

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

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

Rushabh S Shah commented on HDFS-10347:
---------------------------------------

There are 2 approaches:
1. Go through the array of LocatedBlock outside the lock and print every block and then again
go through that array to mark them corrupt.
2. Go through array only once and take a negligible hit for logging within write lock.
We are not looking up any map or data structure so I think the impact is almost negligible.
Any thoughts ?

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


Mime
View raw message