Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Tue, 31 Jan 2012 19:50:10 +0000 (UTC)
From: "Hari Mankude (Created) (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <406312792.12792.1328039410341.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (HDFS-2865) Standby namenode gets a "cannot lock
 storage" exception during startup
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Standby namenode gets a "cannot lock storage" exception during startup
----------------------------------------------------------------------

                 Key: HDFS-2865
                 URL: https://issues.apache.org/jira/browse/HDFS-2865
             Project: Hadoop HDFS
          Issue Type: Bug
            Reporter: Hari Mankude
            Assignee: Hari Mankude


Standby NN is restarted. This is a follow-on to hdfs-2863. In this setup, dfs.edits.dir is different from dfs.shared.edits.dir. During startup, standby NN fails to acquire lock on the dfs.edits.dir. If standby NN is restarted again, it seems to work fine.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira