Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Thu, 11 Oct 2012 17:45:45 +0000 (UTC)
From: "Arun C Murthy (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <570273426.28046.1349977545370.JavaMail.jiratomcat@arcas>
Subject: [jira] [Closed] (HADOOP-8770) NN should not RPC to self to find
 trash defaults (causes deadlock)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Arun C Murthy closed HADOOP-8770.
---------------------------------

    
> NN should not RPC to self to find trash defaults (causes deadlock)
> ------------------------------------------------------------------
>
>                 Key: HADOOP-8770
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8770
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: trash
>    Affects Versions: 2.0.2-alpha
>            Reporter: Todd Lipcon
>            Assignee: Eli Collins
>            Priority: Blocker
>             Fix For: 2.0.2-alpha
>
>         Attachments: hdfs-3876.txt, hdfs-3876.txt, hdfs-3876.txt, hdfs-3876.txt
>
>
> When transitioning a SBN to active, I ran into the following situation:
> - the TrashPolicy first gets loaded by an IPC Server Handler thread. The {{initialize}} function then tries to make an RPC to the same node to find out the defaults.
> - This is happening inside the NN write lock (since it's part of the active initialization). Hence, all of the other handler threads are already blocked waiting to get the NN lock.
> - Since no handler threads are free, the RPC blocks forever and the NN never enters active state.
> We need to have a general policy that the NN should never make RPCs to itself for any reason, due to potential for deadlocks like this.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira