[ https://issues.apache.org/jira/browse/HDFS-4182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13497457#comment-13497457 ]
Hadoop QA commented on HDFS-4182: --------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12553558/HDFS-4182-branch-0.23.txt against trunk revision . {color:red}-1 patch{color}. The patch command could not apply the patch. Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/3504//console This message is automatically generated. > 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-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