[
https://issues.apache.org/jira/browse/HDFS-17187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17764141#comment-17764141
]
qinyuren commented on HDFS-17187:
---------------------------------
*hdfs fsck -blockId <blk_ID>* can get the hdfs file path.
> add the tool that getting the hdfs file path through block id
> -------------------------------------------------------------
>
> Key: HDFS-17187
> URL: https://issues.apache.org/jira/browse/HDFS-17187
> Project: Hadoop HDFS
> Issue Type: New Feature
> Components: hdfs
> Affects Versions: 3.3.6
> Reporter: liying
> Assignee: liying
> Priority: Minor
>
> In some cases, we need to use the block id to get the hdfs file path.
> However, the retention time of hdfs namenode log is limited. Maybe we can't
> get the block information. If you run fsck / -flies -blocks | grep
> '$blockId', you will find that it is very heavy and the hdfs service
> performance is affected. So it is need to add the tool that getting the hdfs
> file path through block id.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
