You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Steve Loughran (Assigned) (JIRA)" <ji...@apache.org> on 2011/09/27 13:45:16 UTC

[jira] [Assigned] (HADOOP-2209) SecondaryNamenode process should exit if it encounters Runtime exceptions

     [ https://issues.apache.org/jira/browse/HADOOP-2209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Loughran reassigned HADOOP-2209:
--------------------------------------

    Assignee: Steve Loughran  (was: dhruba borthakur)
    
> SecondaryNamenode process should exit if it encounters Runtime exceptions
> -------------------------------------------------------------------------
>
>                 Key: HADOOP-2209
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2209
>             Project: Hadoop Common
>          Issue Type: Bug
>            Reporter: dhruba borthakur
>            Assignee: Steve Loughran
>             Fix For: 0.16.0
>
>         Attachments: secondaryExit.patch
>
>
> I saw a case when the SecondaryNamenode encountered a OutOfMemory exception because the fsimage and edits file were too big to fit into the Secondary Namenode's memory. However, the process did not exit.
> Exception in thread "org.apache.hadoop.dfs.SecondaryNameNode@73eb904d" java.lang.OutOfMemoryError: GC overhead limit
> exceeded
>   at java.lang.AbstractStringBuilder.<init>(AbstractStringBuilder.java:45)
>   at java.lang.StringBuffer.<init>(StringBuffer.java:91)
>   at org.apache.hadoop.io.UTF8.toString(UTF8.java:129)
>   at org.apache.hadoop.dfs.FSImage.loadFSImage(FSImage.java:692)
>   at org.apache.hadoop.dfs.SecondaryNameNode.doMerge(SecondaryNameNode.java:304)
>   at org.apache.hadoop.dfs.SecondaryNameNode.doCheckpoint(SecondaryNameNode.java:273)
>   at org.apache.hadoop.dfs.SecondaryNameNode.run(SecondaryNameNode.java:190)
>   at java.lang.Thread.run(Thread.java:619)
> 		

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira