[
https://issues.apache.org/jira/browse/HDFS-11180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15701339#comment-15701339
]
Akira Ajisaka commented on HDFS-11180:
--------------------------------------
Rethinking this, 01 patch is no-op.
Calling synchronized getLastWrittenTxId/getCurSegmentTxId method ensures all
other synchronized methods are not being called. Maybe this behavior is
avoiding some problems. Therefore now I'm thinking it's not better to remove
the synchronization before we conclude that it is safe.
> 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
> Affects Versions: 2.6.0
> Reporter: Abhishek Modi
> Labels: high-availability
> Attachments: HDFS-11180.00.patch, HDFS-11180.01.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]
