[
https://issues.apache.org/jira/browse/HDFS-17380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17824353#comment-17824353
]
ASF GitHub Bot commented on HDFS-17380:
---------------------------------------
Hexiaoqiao commented on PR #6549:
URL: https://github.com/apache/hadoop/pull/6549#issuecomment-1983209877
Hi @szetszwo , Thanks for your works. I am not sure if this is one safe
operations. Now it keeps at least 2 checkpoints by
default(dfs.namenode.num.checkpoints.retained), it configs to more than default
value in production env generally. We should recover from other fsimages first
if one fsimage file is corrupted IMO rather than remove inaccessible nodes then
recover. I am afraid this will be not acceptable in most case. Thanks again.
> FsImageValidation: remove inaccessible nodes
> --------------------------------------------
>
> Key: HDFS-17380
> URL: https://issues.apache.org/jira/browse/HDFS-17380
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: tools
> Reporter: Tsz-wo Sze
> Assignee: Tsz-wo Sze
> Priority: Major
> Labels: pull-request-available
>
> If a fsimage is corrupted, it may have inaccessible nodes. The
> FsImageValidation tool currently is able to identify the inaccessible nodes
> when validating the INodeMap. This JIRA is to update the tool to remove the
> inaccessible nodes and then save a new fsimage.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
