Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Mon, 9 Sep 2013 16:33:51 +0000 (UTC)
From: "Mariappan Asokan (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: <JIRA.12665511.1377528113525.101630.1378744431861@arcas>
In-Reply-To: <JIRA.12665511.1377528113525@arcas>
References: <JIRA.12665511.1377528113525@arcas>
Subject: [jira] [Commented] (MAPREDUCE-5481) TestUberAM timeout
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Mariappan Asokan commented on MAPREDUCE-5481:
---------------------------------------------

I noticed similar timeout on my system.  Although I am not familiar with the code related to this problem, here is what I noticed by looking at the test logs.  The Resource Manager comes up listening on a random free port in localhost like localhost:49170.  When a client(from the test) connects through RMProxy it is trying to resolve localhost through name server(not by local hosts file.)  This causes failure to connect to Resource Manager and after certain number of retries the test timeouts.
                
> TestUberAM timeout
> ------------------
>
>                 Key: MAPREDUCE-5481
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5481
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2, test
>    Affects Versions: 3.0.0
>            Reporter: Jason Lowe
>
> TestUberAM has been timing out on trunk for some time now and surefire then fails the build.  I'm not able to reproduce it locally, but the Jenkins builds have been seeing it fairly consistently.  See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1529/console

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