hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron T. Myers (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4182) SecondaryNameNode leaks NameCache entries
Date Tue, 13 Nov 2012 21:58:12 GMT

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

Aaron T. Myers commented on HDFS-4182:
--------------------------------------

It will probably be a little easier to implement, but I don't feel strongly about it. In ordinary
operation a long-running 2NN doesn't actually load the fsimage every time it performs a checkpoint,
so having the NameCache enabled won't actually do anything after the initial fsimage load.
                
> SecondaryNameNode leaks NameCache entries
> -----------------------------------------
>
>                 Key: HDFS-4182
>                 URL: https://issues.apache.org/jira/browse/HDFS-4182
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: name-node
>    Affects Versions: 0.23.4, 3.0.0, 2.0.2-alpha
>            Reporter: Todd Lipcon
>            Assignee: Robert Joseph Evans
>            Priority: Critical
>         Attachments: HDFS-4182.txt
>
>
> We recently saw an issue where a 2NN ran out of memory, even though it had a relatively
small fsimage. When we looked at the heap dump, we saw that all of the memory had gone to
entries in the NameCache.
> It appears that the NameCache is staying in "initializing" mode forever, and therefore
a long running 2NN leaks entries.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message