[
https://issues.apache.org/jira/browse/HDFS-17380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17824462#comment-17824462
]
ASF GitHub Bot commented on HDFS-17380:
---------------------------------------
szetszwo commented on PR #6549:
URL: https://github.com/apache/hadoop/pull/6549#issuecomment-1983883646
@Hexiaoqiao , thanks for review this!
> ... We should recover from other fsimages first if one fsimage file is
corrupted ...
This may not be acceptable in some use cases since the newly created files
will be lost (i.e. data loss) if we recover from an earlier fsimage. If we
remove the inaccessible inodes, we won't lose any files (i.e. no data loss).
BTW, this is just a tool to fix fsimages. Users may choose not to use it if
they are fine to recover from an earlier fsimage.
> 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]
