You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Siyao Meng (JIRA)" <ji...@apache.org> on 2018/08/09 23:13:00 UTC
[jira] [Commented] (HDFS-13813) Exit NameNode if dangling child
inode is detected when saving FsImage
[ https://issues.apache.org/jira/browse/HDFS-13813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16575535#comment-16575535 ]
Siyao Meng commented on HDFS-13813:
-----------------------------------
v001 jenkins: Tested TestBalancerWithMultipleNameNodes, TestFailureToReadEdits and TestDFSClientRetries locally and passed all.
Pending v002 jenkins.
> Exit NameNode if dangling child inode is detected when saving FsImage
> ---------------------------------------------------------------------
>
> Key: HDFS-13813
> URL: https://issues.apache.org/jira/browse/HDFS-13813
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: hdfs, namenode
> Affects Versions: 3.1.0, 2.10.0, 2.9.1, 3.0.3
> Reporter: Siyao Meng
> Assignee: Siyao Meng
> Priority: Major
> Attachments: HDFS-13813.001.patch, HDFS-13813.002.patch
>
>
> Recently, the same stack trace as in -HDFS-9406- appears again in the field. The symptom of the problem is that *loadINodeDirectorySection()* can't find a child inode in inodeMap by the node id in the children list of the directory. The child inode could be missing or deleted.
> As for now we didn't have a clear trace to reproduce the problem. Therefore, I'm proposing this improvement to detect such corruption (data structure inconsistency) when saving the FsImage, so that we can have the FsImage and Edit Log to hopefully reproduce the problem stably.
>
> In a previous patch HDFS-13314, [~arpitagarwal] did a great job catching potential FsImage corruption in two cases. This patch includes a third case where a child inode does not exist in the global FSDirectory dir when saving (serializing) INodeDirectorySection.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org