You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2008/08/22 14:34:50 UTC
[jira] Commented: (HADOOP-3865) SecondaryNameNode runs out of
memory
[ https://issues.apache.org/jira/browse/HADOOP-3865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12624745#action_12624745 ]
Hudson commented on HADOOP-3865:
--------------------------------
Integrated in Hadoop-trunk #581 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/581/])
> 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.