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 "Kihwal Lee (JIRA)" <ji...@apache.org> on 2015/10/08 19:39:26 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 ]
Kihwal Lee updated HADOOP-10219:
--------------------------------
Attachment: HADOOP-10219.patch
I manually tested this patch in a non-ha env. ^C now kills the main thread that is stuck in making connection.
> 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, 2.6.0
> Reporter: Steve Loughran
> Attachments: HADOOP-10219.patch
>
>
> 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.3.4#6332)