hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Akira Ajisaka (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-11180) Intermittent deadlock in NameNode when failover happens.
Date Mon, 28 Nov 2016 06:40:58 GMT

    [ https://issues.apache.org/jira/browse/HDFS-11180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15701113#comment-15701113

Akira Ajisaka commented on HDFS-11180:

Thank you for your information.
It looks like:
* NameNode holds a lock of FSEditLog and requires a lock of MetricsSystemImpl when registering
IPCLoggerChannel metrics.
* At the same time, metrics system holds a lock of MetricsSystemImpl and requires a lock of
FSEditLog when publishing FSNameSystem.TransactionsSinceLastCheckpoint metric.

I'm thinking we don't need to hold a lock when publishing FSNameSystem.TransactionsSinceLastCheckpoint

> 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: 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

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message