Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Wed, 7 Nov 2012 15:21:12 +0000 (UTC)
From: "Kihwal Lee (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <288426035.80812.1352301672829.JavaMail.jiratomcat@arcas>
In-Reply-To: <306576613.57903.1351804692781.JavaMail.jiratomcat@arcas>
Subject: [jira] [Updated] (HDFS-4138) BackupNode startup fails due to
 uninitialized edit log
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Kihwal Lee updated HDFS-4138:
-----------------------------

    Attachment: hdfs-4138.patch

Here is a new patch that sets the block pool id, less initialization changes.
                
> 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