[ 
https://issues.apache.org/jira/browse/HDFS-7611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Konstantin Shvachko updated HDFS-7611:
--------------------------------------
          Component/s: namenode
          Description: 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.  (was: 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.)
             Priority: Critical  (was: Major)
     Target Version/s: 2.7.0  (was: 3.0.0)
    Affects Version/s:     (was: 3.0.0)
                       2.6.0
              Summary: deleteSnapshot and delete of a file can leave orphaned 
blocks in the blocksMap on NameNode restart.  (was: 
TestFileTruncate.testTruncateEditLogLoad times out waiting for Mini HDFS 
Cluster to start)

Changed the description. It used to be: 
TestFileTruncate.testTruncateEditLogLoad times out waiting for Mini HDFS 
Cluster to start.

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

Reply via email to