hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-2865) Standby namenode gets a "cannot lock storage" exception during startup
Date Thu, 02 Feb 2012 00:47:54 GMT

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

Todd Lipcon updated HDFS-2865:
------------------------------

    Attachment: hdfs-2865.txt

Attached patch fixes the issue. It's not possible to write a unit test for this, since it
relies on triggering the deleteOnExit hook. To test, I set up two NNs which pointed to the
same dir. When I started the second, it failed with a lock error, but didn't delete the lock
file.
                
> 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: Sub-task
>          Components: ha, name-node
>    Affects Versions: HA branch (HDFS-1623)
>            Reporter: Hari Mankude
>            Assignee: Hari Mankude
>         Attachments: hdfs-2865.txt
>
>
> 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

        

Mime
View raw message