hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Shvachko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-7611) deleteSnapshot and delete of a file can leave orphaned blocks in the blocksMap on NameNode restart.
Date Wed, 28 Jan 2015 07:19:35 GMT

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

Konstantin Shvachko commented on HDFS-7611:
-------------------------------------------

Jing, unfortunately I just reproduce failure of {{TestOpenFilesWithSnapshot}} after running
it seven times. It is intermittent, we knew that. Let me look more closely tomorrow. I just
want to make sure it is not the same problem, because this test also does delete snapshot
then delete.

> deleteSnapshot and delete of a file can leave orphaned blocks in the blocksMap on NameNode
restart.
> ---------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-7611
>                 URL: https://issues.apache.org/jira/browse/HDFS-7611
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 2.6.0
>            Reporter: Konstantin Shvachko
>            Assignee: Byron Wong
>            Priority: Critical
>         Attachments: HDFS-7611.000.patch, HDFS-7611.001.patch, HDFS-7611.002.patch, blocksNotDeletedTest.patch,
testTruncateEditLogLoad.log
>
>
> If quotas are enabled a combination of operations *deleteSnapshot* and *delete* of a
file can leave  orphaned  blocks in the blocksMap on NameNode restart. They are counted as
missing on the NameNode, and can prevent NameNode from coming out of safeMode and could cause
memory leak during startup.



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

Mime
View raw message