Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-dev@hadoop.apache.org
Date: Sat, 21 Jan 2012 02:48:39 +0000 (UTC)
From: "Aaron T. Myers (Created) (JIRA)" <jira@apache.org>
To: hdfs-dev@hadoop.apache.org
Message-ID: 
 <979532600.62562.1327114119748.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (HDFS-2823) HA: Transition to active can cause NN
 deadlock
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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 thread.

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