Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Mon, 25 Jan 2016 19:17:39 +0000 (UTC)
From: "Yongjun Zhang (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12933881.1453742876000.203600.1453749459922@Atlassian.JIRA>
In-Reply-To: <JIRA.12933881.1453742876000@Atlassian.JIRA>
References: <JIRA.12933881.1453742876000@Atlassian.JIRA>
 <JIRA.12933881.1453742876835@arcas>
Subject: [jira] [Commented] (HDFS-9696) Garbage snapshot records lingering
 forever
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Yongjun Zhang commented on HDFS-9696:
-------------------------------------

Thanks Kihwal. Yes, agree. While I have been investigating, I indeed planned to ask the snapshot developers for help at some point.


> 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)