hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron T. Myers (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HDFS-2823) HA: Transition to active can cause NN deadlock
Date Sat, 21 Jan 2012 02:58:39 GMT

     [ https://issues.apache.org/jira/browse/HDFS-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Aaron T. Myers resolved HDFS-2823.

    Resolution: Invalid

I forgot that HDFS-2737 hasn't been committed yet, and this bug is only present in the latest
patch for that JIRA. Resolving this and will post an updated patch on HDFS-2737.
> HA: Transition to active can cause NN deadlock
> ----------------------------------------------
>                 Key: HDFS-2823
>                 URL: https://issues.apache.org/jira/browse/HDFS-2823
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: ha, name-node
>    Affects Versions: HA branch (HDFS-1623)
>            Reporter: Aaron T. Myers
>            Assignee: Aaron T. Myers
>            Priority: Blocker
> On transition to active, we have to take the FSNS write lock. In {{EditLogTailer#stop}},
we interrupt the edit log tailer thread and then join on that thread. When tailing edits,
the edit log tailer thread acquires the FSNS write lock interruptibly, precisely so that we
avoid deadlocks on transition to active. However, the edit log tailer thread now also triggers
edit log rolls. Several places in {{ipc.Client}} catch and ignore {{InterruptedException}},
and in so doing may cause the {{Thread#interrupt}} call to be missed by the edit log tailer

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message