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) TestFileTruncate.testTruncateEditLogLoad times out waiting for Mini HDFS Cluster to start
Date Thu, 22 Jan 2015 01:03:47 GMT

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

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

Byron, good job investigating and reproducing the bug.
Sounds like a serious problem. I also confirmed it on branch-2 with your test.

_So 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 (at least during startup)._

I'll rename the jira and unlink from HDFS-3107 as it is not related to truncate.

> TestFileTruncate.testTruncateEditLogLoad times out waiting for Mini HDFS Cluster to start
> -----------------------------------------------------------------------------------------
>
>                 Key: HDFS-7611
>                 URL: https://issues.apache.org/jira/browse/HDFS-7611
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 3.0.0
>            Reporter: Konstantin Shvachko
>            Assignee: Byron Wong
>         Attachments: blocksNotDeletedTest.patch, testTruncateEditLogLoad.log
>
>
> I've seen it failing on Jenkins a couple of times. Somehow the cluster is not comming
ready after NN restart.
> Not sure if it is truncate specific, as I've seen same behaviour with other tests that
restart the NameNode.



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

Mime
View raw message