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 "Steve Loughran (JIRA)" <ji...@apache.org> on 2014/01/10 16:48:51 UTC

[jira] [Updated] (HADOOP-10219) ipc.Client.setupIOstreams() needs to check for ClientCache.stopClient requested shutdowns

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

Steve Loughran updated HADOOP-10219:
------------------------------------

    Summary: ipc.Client.setupIOstreams() needs to check for ClientCache.stopClient requested shutdowns   (was: pc.Client.setupIOstreams() needs to check for ClientCache.stopClient requested shutdowns )

> ipc.Client.setupIOstreams() needs to check for ClientCache.stopClient requested shutdowns 
> ------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-10219
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10219
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: ipc
>    Affects Versions: 2.2.0
>            Reporter: Steve Loughran
>            Priority: Minor
>
> When {{ClientCache.stopClient()}} is called to stop the IPC client, if the client
> is blocked spinning due to a connectivity problem, it does not exit until the policy has timed out -so the stopClient() operation can hang for an extended period of time.
> This can surface in the shutdown hook of FileSystem.cache.closeAll()



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)