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 2018/09/04 15:46:00 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16603222#comment-16603222 ]
Steve Loughran commented on HADOOP-10219:
-----------------------------------------
silence from others. So I've had a look again, and I don't see it being risky
+1
> 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
> Assignee: Kihwal Lee
> Priority: Major
> Attachments: HADOOP-10219.patch, HADOOP-10219.v1.patch, HADOOP-10219.v2.patch, HADOOP-10219.v3.patch, HADOOP-10219.v4.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()
> Also, Client.stop() is for used in NN switch from Standby to Active, and can therefore have very bad consequences and cause downtime.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org