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:49:12 GMT

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

Kihwal Lee commented on HDFS-4138:

It is normally okay and actually desired as explained in HDFS-3573. In FSNamesystem.loadFromDisk(),
loadFSImage() is called right after loading the NamespaceInfo, so the edit log is initialized
by the time loadNamesystem() is done.  Only BackupNode overrides loadNamesystem(), the solution
will be adding a call to FSImage#initEditLog() before returning.
> 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
>            Assignee: 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

View raw message