[
https://issues.apache.org/jira/browse/HADOOP-9655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13705483#comment-13705483
]
Hadoop QA commented on HADOOP-9655:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12591789/HADOOP-9655.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-common-project/hadoop-common.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/2767//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/2767//console
This message is automatically generated.
> 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
