hadoop-hdfs-issues mailing list archives

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

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

Abhishek Modi commented on HDFS-11180:
--------------------------------------

Can we have a separate readWrite lock for txid? We will acquire readLock in FSEditLog.getLastWrittenTxId
and writeLock in FSEditLog.beginTransaction and FSEditLog.setNextTxId. This way, we would
be safely able to read TxId in FsNamesystem.getTransactionsSinceLastCheckpoint. Thoughts?

> 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, 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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org


Mime
View raw message