Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Mon, 20 Feb 2012 08:17:41 +0000 (UTC)
From: "Matt Foley (Reopened) (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: 
 <1961306583.1859.1329725861709.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <731086539.21005.1328819457282.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Reopened] (HADOOP-8050) Deadlock in metrics
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Matt Foley reopened HADOOP-8050:
--------------------------------


The Commit integration to both trunk and v0.23 succeeded with common and hdfs, but aborted in mapreduce.  The log records:
{code}
ivy-resolve-mapred:
Build timed out (after 45 minutes). Marking the build as aborted.
Build was aborted
Recording test results
None of the test reports contained any result
Updating HADOOP-8050
No emails were triggered.
Finished: ABORTED
{code}

This looks more like a connectivity issue with ivy than a problem with the patch, but re-opening pending investigation.
                
> Deadlock in metrics
> -------------------
>
>                 Key: HADOOP-8050
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8050
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: metrics
>    Affects Versions: 0.20.204.0, 0.20.205.0, 0.23.0, 1.0.0
>            Reporter: Kihwal Lee
>            Assignee: Kihwal Lee
>             Fix For: 1.0.1, 0.23.2
>
>         Attachments: hadoop-8050-branch-1.patch.txt, hadoop-8050-branch-1.patch.txt, hadoop-8050-branch-1.patch.txt, hadoop-8050-branch-1.patch.txt, hadoop-8050-trunk.patch.txt, hadoop-8050-trunk.patch.txt, hadoop-8050-trunk.patch.txt, hadoop-8050.patch.txt
>
>
> The metrics serving thread and the periodic snapshot thread can deadlock.
> It happened a few times on one of namenodes we have. When it happens RPC works but the web ui and hftp stop working. I haven't look at the trunk too closely, but it might happen there too.

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