[
https://issues.apache.org/jira/browse/HADOOP-5019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12663905#action_12663905
]
Tsz Wo (Nicholas), SZE commented on HADOOP-5019:
------------------------------------------------
> I agree with Steve. If a user has write permission to the file, then he/she
> should be able to find information about this block.
I disagree. Write permission should only mean write to the file but not
anything else.
The permission requirement for reading file meta data such as file size is x on
the parent directory. It seems that this block query operation should do the
same.
However, considering that block details like block IDs, generation stamps, etc.
should be invisible to users in general. I think it makes sense to require
superuser.
> add querying block's info in the fsck facility
> ----------------------------------------------
>
> Key: HADOOP-5019
> URL: https://issues.apache.org/jira/browse/HADOOP-5019
> Project: Hadoop Core
> Issue Type: New Feature
> Components: dfs
> Reporter: zhangwei
> Priority: Minor
> Attachments: 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
