hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jing Zhao (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-9696) Garbage snapshot records lingering forever
Date Mon, 25 Jan 2016 19:32:39 GMT

    [ https://issues.apache.org/jira/browse/HDFS-9696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15115818#comment-15115818
] 

Jing Zhao commented on HDFS-9696:
---------------------------------

Currently I think HDFS-9406 and HDFS-9697 may both be caused by some lingering INode in the
diff list. Both failed when loading INode from the inode Map. Compared with the logic for
removing inodes from inode map, cleaning diff list is more complicated thus has higher chance
to fail.

> Garbage snapshot records lingering forever
> ------------------------------------------
>
>                 Key: HDFS-9696
>                 URL: https://issues.apache.org/jira/browse/HDFS-9696
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 2.7.2
>            Reporter: Kihwal Lee
>            Assignee: Yongjun Zhang
>            Priority: Critical
>
> We have a cluster where the snapshot feature might have been tested years ago. When the
HDFS does not have any snapshot, but I see filediff records persisted in its fsimage.  Since
it has been restarted many times and checkpointed over 100 times since then, it must haven
been persisted and  carried over since then.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message