hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-207) add querying block's info in the fsck facility
Date Mon, 21 Jul 2014 18:02:40 GMT

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

Allen Wittenauer commented on HDFS-207:
---------------------------------------

Ping!

> add querying block's info in the fsck facility
> ----------------------------------------------
>
>                 Key: HDFS-207
>                 URL: https://issues.apache.org/jira/browse/HDFS-207
>             Project: Hadoop HDFS
>          Issue Type: New Feature
>          Components: namenode
>            Reporter: zhangwei
>            Assignee: zhangwei
>            Priority: Minor
>         Attachments: HADOOP-5019-2.patch, HADOOP-5019.patch
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> As now the fsck can do pretty well,but when the developer happened to the log such Block
blk_28622148 is not valid.etc
> We wish to know which file and the datanodes the block belongs to.It  can be solved by
running "bin/hadoop fsck -files -blocks -locations / | grep <blockid>" ,but as mentioned
early in the HADOOP-4945 ,it's not an effective way in a big product cluster.
> so maybe we could do something to let the fsck more convenience .



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message