[
https://issues.apache.org/jira/browse/HDFS-11180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15778658#comment-15778658
]
Erik Krogen commented on HDFS-11180:
------------------------------------
[~ajisakaa], sorry, I should have specified - I was looking at branch-2.7.
However, even in branch-2 and trunk, {{FSImage#getLastAppliedOrWrittenTxId}}
internally calls {{FSEditLog#getLastWrittenTxId}}, presenting the same problem
that to complete the metrics call eventually requires synchronization on the
{{FSEditLog}}.
> 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: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
