hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kihwal Lee (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4138) BackupNode startup fails due to uninitialized edit log
Date Fri, 02 Nov 2012 15:33:16 GMT

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

Kihwal Lee commented on HDFS-4138:
----------------------------------

When BackupNode is coming up, the following happens.

1. BackupNode#initialize() calls NameNode#initialize().
2.   NameNode#initialize() calls loadNamesystem(), which instantiates an FsImage (or BackupImage)
object.
3.   It also calls startCommonServices(), which calls DefaultMetricsSystem.instance().register().
4. BackupNode#initialize() then calls runCheckpointDaemon(conf)


Before HDFS-3573, FSImage's ctor would initialize the edit log in step 2, so next steps worked.
After HDFS-3573, the edit log is not initialized when step 3 and 4 run, thus causing the two
exceptions reported above and failing backup node startup.


                
> BackupNode startup fails due to uninitialized edit log
> ------------------------------------------------------
>
>                 Key: HDFS-4138
>                 URL: https://issues.apache.org/jira/browse/HDFS-4138
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: ha, name-node
>    Affects Versions: 2.0.3-alpha
>            Reporter: Kihwal Lee
>
> It was notices by TestBackupNode.testCheckpointNode failure. When a backup node is getting
started, it tries to enter active state and start common services. But when it fails to start
services and exits, which is caught by the exit util.

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

Mime
View raw message