Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Thu, 11 Jul 2013 06:09:50 +0000 (UTC)
From: "nemon lou (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12653846.1371699333901.31123.1373522990088@arcas>
In-Reply-To: <JIRA.12653846.1371699333901@arcas>
References: <JIRA.12653846.1371699333901@arcas>
Subject: [jira] [Commented] (HADOOP-9655) IPC Client call to the same host
 with multi thread takes very long time to report connection time out for
 many times
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

nemon lou commented on HADOOP-9655:
-----------------------------------

This patch has been tested on my cluster and has solved the problem.
                
> IPC Client call to the same host with multi thread takes very long time to report connection time out for many times 
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-9655
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9655
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: ipc
>    Affects Versions: 2.0.4-alpha
>            Reporter: nemon lou
>         Attachments: HADOOP-9655.patch
>
>
> When one machine power off during running a job ,MRAppMaster find tasks timed out on that host and then call stop container for each container concurrently.
> But the IPC layer did it serially, for each call,the connection time out exception toke a few minutes to raise after 45 times reties. And AM hang for many hours to wait for stopContainer to finish.
> The jstack output file shows that most threads stuck at Connection.addCall waiting for a lock object hold by  Connection.setupIOstreams.
> (The setupIOstreams method run slowlly becauseof connection time out during setupconnection.)

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