[
https://issues.apache.org/jira/browse/HADOOP-3865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12618779#action_12618779
]
Lohit Vijayarenu commented on HADOOP-3865:
------------------------------------------
Test failures are un-related to this patch HADOOP-3874 and HADOOP-3882 have
been opened to track this.
I tested test-patch and ran tests on 0.18. They pass.
> SecondaryNameNode runs out of memory
> ------------------------------------
>
> Key: HADOOP-3865
> URL: https://issues.apache.org/jira/browse/HADOOP-3865
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.18.0
> Reporter: Lohit Vijayarenu
> Assignee: Lohit Vijayarenu
> Priority: Blocker
> Fix For: 0.18.0
>
> Attachments: HADOOP-3865-18.patch, HADOOP-3865-18.patch,
> HADOOP-3865-18.patch, HADOOP-3865-trunk.patch, HADOOP-3865-trunk.patch,
> HADOOP-3865-trunk.patch
>
>
> SecondaryNameNode has memory leak. If we leave secondary namenode to run for
> a while doing several checkpoints it runs out of heap.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
