You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Aaron T. Myers (JIRA)" <ji...@apache.org> on 2012/10/15 23:47:03 UTC

[jira] [Commented] (HDFS-3678) Edit log files are never being purged from 2NN

    [ https://issues.apache.org/jira/browse/HDFS-3678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13476492#comment-13476492 ] 

Aaron T. Myers commented on HDFS-3678:
--------------------------------------

I'd like to merge this change to branch-2 as well. It's not strictly necessary because this bug doesn't exist in branch-2, but merging this restructuring of the code to branch-2 will make future merges in related code easier.

If I don't hear any objections I'm going to do this late today some time, so please speak up.
                
> Edit log files are never being purged from 2NN
> ----------------------------------------------
>
>                 Key: HDFS-3678
>                 URL: https://issues.apache.org/jira/browse/HDFS-3678
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: name-node
>    Affects Versions: 3.0.0
>            Reporter: Todd Lipcon
>            Assignee: Aaron T. Myers
>            Priority: Critical
>             Fix For: 3.0.0
>
>         Attachments: HDFS-3678.patch, HDFS-3678.patch, HDFS-3678.patch
>
>
> Seeing the following NPE in the SecondaryNameNode when it tries to purge storage after a checkpoint:
> 12/07/17 19:05:22 WARN namenode.FSImage: Unable to purge old storage
> java.lang.NullPointerException
>         at org.apache.hadoop.hdfs.server.namenode.FSEditLog.purgeLogsOlderThan(FSEditLog.java:1013)
>         at org.apache.hadoop.hdfs.server.namenode.NNStorageRetentionManager.purgeOldStorage(NNStorageRetentionManager.java:98)
>         at org.apache.hadoop.hdfs.server.namenode.FSImage.purgeOldStorage(FSImage.java:925)
>         at org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode.doCheckpoint(SecondaryNameNode.java:479)

--
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