[
https://issues.apache.org/jira/browse/HDFS-11180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Modi updated HDFS-11180:
---------------------------------
Comment: was deleted
(was: We have set:
<property>
<name>dfs.namenode.name.dir</name>
<value>
/media/ephemeral0/dfs/namenode,/media/ephemeral1/dfs/namenode
</value>
<property>
<name>dfs.namenode.shared.edits.dir</name>
<value>
qjournal://ec2-54-92-238-125.compute-1.amazonaws.com:8485;ec2-54-163-80-110.compute-1.amazonaws.com:8485;ec2-54-197-119-189.compute-1.amazonaws.com:8485/HACluster
</value>
</property>
We just followed the documentation for HA. What is the recommended settings for
these parameters?)
> Intermittent deadlock in NameNode when failover happens.
> --------------------------------------------------------
>
> Key: HDFS-11180
> URL: https://issues.apache.org/jira/browse/HDFS-11180
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 2.6.0
> Reporter: Abhishek Modi
> Assignee: Akira Ajisaka
> Priority: Blocker
> Labels: high-availability
> Fix For: 2.8.0, 2.7.4, 3.0.0-alpha2, 2.6.6
>
> Attachments: HDFS-11180-branch-2.01.patch,
> HDFS-11180-branch-2.6.01.patch, HDFS-11180-branch-2.7.01.patch,
> HDFS-11180-branch-2.8.01.patch, HDFS-11180.00.patch, HDFS-11180.01.patch,
> HDFS-11180.02.patch, HDFS-11180.03.patch, HDFS-11180.04.patch, jstack.log
>
>
> It is happening due to metrics getting updated at the same time when failover
> is happening. Please find attached jstack at that point of time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
