hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Shvachko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4138) BackupNode startup fails due to uninitialized edit log
Date Wed, 07 Nov 2012 07:00:35 GMT

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

Konstantin Shvachko commented on HDFS-4138:
-------------------------------------------

After examining more the current state of BN I think we should stick with the extra condition
in getTransactionsSinceLastLogRoll() and not change the order of initialization at this point.
In the end it is right to return 0, because there were no rolls in the beginning.
I further found that we do not set blockPoolId in BN.namesystem, which we should. Let's add
{code}namesystem.setBlockPoolId(nsInfo.getBlockPoolID());{code} and get that committed.
                
> 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
>         Attachments: hdfs-4138.patch, hdfs-4138.patch, hdfs-4138.patch, hdfs-4138.patch
>
>
> 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