[
https://issues.apache.org/jira/browse/HDFS-2865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13197491#comment-13197491
]
Hari Mankude commented on HDFS-2865:
------------------------------------
Both these are nfs directories. Lock issue is with name.dir
<property>
<name>dfs.name.dir</name>
<value>/homes/hortonha/namenode/fsimage</value>
</property>
<property>
<name>dfs.namenode.shared.edits.dir</name>
<value>/homes/hortonha/namenode</value>
</property>
> 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
>
> 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
