[
https://issues.apache.org/jira/browse/HDFS-4182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13497922#comment-13497922
]
Hudson commented on HDFS-4182:
------------------------------
Integrated in Hadoop-Yarn-trunk #37 (See
[https://builds.apache.org/job/Hadoop-Yarn-trunk/37/])
HDFS-4182. SecondaryNameNode leaks NameCache entries (bobby) (Revision
1409311)
Result = SUCCESS
bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1409311
Files :
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSDirectory.java
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/NameCache.java
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/SecondaryNameNode.java
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestFSDirectory.java
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestNameCache.java
> 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
> Fix For: 3.0.0, 2.0.3-alpha, 0.23.5
>
> Attachments: HDFS-4182-branch-0.23.txt, HDFS-4182.txt, HDFS-4182.txt,
> HDFS-4182.txt, 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
