You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2015/05/06 05:38:10 UTC

[jira] [Updated] (HADOOP-9655) Connection object in IPC Client can not run concurrently during connection time out

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

Allen Wittenauer updated HADOOP-9655:
-------------------------------------
    Labels: BB2015-05-TBR  (was: )

> Connection object in IPC Client can not run concurrently during connection time out
> -----------------------------------------------------------------------------------
>
>                 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
>              Labels: BB2015-05-TBR
>         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 was sent by Atlassian JIRA
(v6.3.4#6332)