[
https://issues.apache.org/jira/browse/HDFS-11180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akira Ajisaka updated HDFS-11180:
---------------------------------
Release Note:
<!-- markdown -->
After this fix, the value of the following metrics/JMX can be incorrect.
* LastWrittenTransactionId (FSNameSystem)
* TotalSyncCount (FSNameSystem)
* TransactionsSinceLastLogRoll (FSNameSystem)
* TransactionsSinceLastCheckpoint (FSNameSystem)
* NameJournalStatus (NameNodeMXBean)
* JournalTransactionInfo (NameNodeMXBean)
This is due to the removal of holding lock of FSEditLog when acquiring the
value of the metrics/JMX.
Component/s: namenode
> 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
> Attachments: 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]
